MaxKB is an open-source AI assistant for enterprise. In 2.7.0 through 2.10.4-lts, POST /chat/api/{application_id}/chat/{chat_id}/share_chat verifies that a conversation exists but does not verify that it belongs to the authenticated chat_user_id or to the application bound to the caller's token. An attacker with any chat token and a known victim chat_id can create an unauthenticated public ChatShareLink exposing the victim's conversation and can create PublicFileAccess state that makes associated files retrievable without credentials, with no available revoke path. No fixed version is available as of this review.
CVE-2026-79917
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% 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
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 29(Track)EG Risk 29/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 computedSeverity65% × 45%Exploitation0% × 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, 2026Chat share-link endpoint missing owner check: a chat token can publish another user's conversation · Advisory · 1Panel-dev/MaxKB · GitHub
https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-m8gr-554p-8r82Weakness Classification(2)
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 19:27 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-23 17:54 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 16:22 UTCEG score recompute
- 2026-09-22 16:01 UTCEPSS rescore
- 2026-09-22 15:45 UTCEG score recompute
- 2026-09-21 21:22 UTCEG score recompute
- 2026-09-21 20:48 UTCEG score recompute
- 2026-09-21 20:47 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-79917?
When was CVE-2026-79917 disclosed?
Is CVE-2026-79917 actively exploited?
What is the CVSS score of CVE-2026-79917?
How do I remediate CVE-2026-79917?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-79917
Is Your Infrastructure Affected by CVE-2026-79917?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.