CVE-2026-77519Public exploitNetwork attack vectorHinoki check available

Expired-key access via omitted MCP expiration checks

Published Sep 21, 2026 · Updated Sep 21, 2026

Insufficient session expiration in KubeOperator MaxKB 2.10.2-lts and earlier allows remote authenticated users to invoke MCP tools with expired keys. The /chat/api/mcp MCPToolHandler queries ApplicationApiKey by secret_key and is_active=True but omits the is_permanent and expire_time checks used by standard chat authentication. Exploitation requires a previously valid non-permanent key that remains active after expiration and a published application; it exposes tool metadata, permits tools/call, and creates durable chat records.

CVSS severity5.4
Medium
EPSS probability0.24%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Insufficient session expiration in KubeOperator MaxKB 2.10.2-lts and earlier allows remote authenticated users to invoke MCP tools with expired keys. The /chat/api/mcp MCPToolHandler queries ApplicationApiKey by secret_key and is_active=True but omits the is_permanent and expire_time checks used by standard chat authentication. Exploitation requires a previously valid non-permanent key that remains active after expiration and a published application; it exposes tool metadata, permits tools/call, and creates durable chat records.

The record

CVE
CVE-2026-77519
Published
Sep 21, 2026
Updated
Sep 21, 2026
Vendor
KubeOperator
Product
MaxKB
Classifications
CWE-613, T1078
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 21, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 21, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=<= 2.10.2-lts

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

KubeOperator · MaxKBversion=<= 2.10.2-lts

Published CVSS scores

5.4GitHub Security AdvisoryCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-613Insufficient Session Expiration
T1078Valid Accounts

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started