Back to CVE records
Medium 5.4Published Sep 21, 2026

CVE-2026-77519MaxKB: Expired application API keys remain usable on `/chat/api/mcp`

Updated under an hour ago ()

Does this affect you?

It affects 1Panel-dev MaxKB. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

MaxKB is an open-source AI assistant for enterprise. In 2.10.2-lts and earlier, the /chat/api/mcp authentication path looks up an ApplicationApiKey using only its secret and active status, without enforcing the is_permanent and expire_time checks used by the standard chat API. A previously valid, non-permanent application key that remains active after expiration can initialize the MCP endpoint, list the published application's tool metadata, invoke tools/call, and create durable application_chat and application_chat_record state even though /chat/api/open rejects the same key. No fixed version is available as of this review.

CVSS
5.4 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Weakness (CWE)
CWE-613
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
GitHub_M
NVD analysis
Deferred
Record last updated
Sep 24, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
1Panel-dev MaxKB
1panel_dev:maxkb (from the name)
through 2.10.2-lts
CNA record

References

  • x-refsource-confirm

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.