MaxKB is an open-source AI assistant for enterprise. In 2.10.2-lts and earlier, a normal workspace user who knows another user's active MCP tool_id in the same workspace can retrieve the hidden tool through the tool-detail route because it does not apply the per-resource authorization used by the list route. The response includes Tool.code, which may contain MCP server configuration and headers, and an attacker who can create or edit an attacker-owned workflow can place the same foreign mcp_tool_id in a workflow mcp-node so workflow debug uses the owner's MCP configuration without verifying permission to use that tool. No fixed version is available as of this review.
CVE-2026-77518
This medium-severity CVE scores 5.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 90% 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.0
- EG Score
- 5.0(medium)
- EG Risk
- 39(Track)EG Risk 39/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 computedSeverity50% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 17%
- KEV
- Not listed
Published
September 21, 2026
Last Modified
September 22, 2026
Advisory Details (1)
Auto-updated Sep 21, 2026MaxKB: Known MCP tool IDs expose owner Tool.code and can be referenced by attacker workflows · Advisory · 1Panel-dev/MaxKB · GitHub
https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-x65c-w438-c58fWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× 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 14:04 UTCEPSS rescore
- 2026-09-24 12:49 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 13:35 UTCEG score recompute
- 2026-09-22 16:01 UTCEPSS rescore
- 2026-09-22 14:20 UTCEG score recompute
- 2026-09-22 13:27 UTCEG score recompute
- 2026-09-21 21:22 UTCEG score recompute
- 2026-09-21 20:43 UTCEG score recompute
- 2026-09-21 20:42 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-77518?
When was CVE-2026-77518 disclosed?
Is CVE-2026-77518 actively exploited?
What is the CVSS score of CVE-2026-77518?
How do I remediate CVE-2026-77518?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-77518
Is Your Infrastructure Affected by CVE-2026-77518?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.