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.
CVE-2026-77519
This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(medium)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity54% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 19%
- KEV
- Not listed
Published
September 21, 2026
Last Modified
September 24, 2026
Advisory Details (1)
Auto-updated Sep 21, 2026MaxKB: Expired application API keys remain usable on `/chat/api/mcp` · Advisory · 1Panel-dev/MaxKB · GitHub
https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-r6g6-69fh-c39qWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-24 23:37 UTCEG score recompute
- 2026-09-24 22:52 UTCEG score recompute
- 2026-09-24 17:59 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-23 19:07 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 20:01 UTCEG score recompute
- 2026-09-22 16:01 UTCEPSS rescore
- 2026-09-21 21:22 UTCEG score recompute
- 2026-09-21 20:33 UTCEG score recompute
- 2026-09-21 20:32 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-77519?
When was CVE-2026-77519 disclosed?
Is CVE-2026-77519 actively exploited?
What is the CVSS score of CVE-2026-77519?
How do I remediate CVE-2026-77519?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-77519
Is Your Infrastructure Affected by CVE-2026-77519?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.