AnythingLLM is an application that turns pieces of content into context that any LLM can use as references during chatting. In 1.11.1 and earlier, On default installations where no password or API key has been configured, all HTTP endpoints and the agent WebSocket lack authentication, and the server's CORS policy accepts any origin. AnythingLLM Desktop binds to 127.0.0.1 (loopback) by default. Modern browsers (Chrome, Edge, Firefox) implement Private Network Access (PNA). This explicitly blocks public websites from making requests to local IP addresses. Exploitation is only viable from within the same local network (LAN) due to browser-level blocking of public-to-private requests.
CVE-2026-32617
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(low)
- EG Risk
- 38(Track)EG Risk 38/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 computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
March 16, 2026
Last Modified
June 17, 2026
References (1)
- security-advisories@githubhttps://github.com/Mintplex-Labs/anything-llm/security/advisories/GHSA-24qj-pw4h-3jmm
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× 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-07-27 14:43 UTCEG score recompute
- 2026-07-27 14:27 UTCOSV refresh
Related CVEs(same CWE)
Same CWE
10 shownCWE-1188
- CVE-2017-7964EG 10.0CRITICAL
- CVE-2020-27555EG 9.8CRITICAL
- CVE-2020-26510EG 9.8CRITICAL
- CVE-2020-13927EG 9.8 KEVEPSS p100CRITICAL
- CVE-2020-10279EG 9.8CRITICAL
- CVE-2020-14011EG 9.8EPSS p98CRITICAL
- CVE-2020-11532EG 9.8EPSS p100CRITICAL
- CVE-2014-0234EG 9.8CRITICAL
- CVE-2019-16272EG 9.8CRITICAL
- CVE-2019-4621EG 9.8CRITICAL
Frequently asked(4)
What is CVE-2026-32617?
When was CVE-2026-32617 disclosed?
What is the CVSS score of CVE-2026-32617?
How do I remediate CVE-2026-32617?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-32617
Is Your Infrastructure Affected by CVE-2026-32617?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.