ArcadeDB versions 26.4.2 through 26.7.3 contain an authorization bypass vulnerability in the set_server_setting MCP server-level tool. SetServerSettingTool.execute() gates only on the global allowAdmin flag and never checks the caller's role, so in an MCP deployment with allowAdmin=true and a non-root allowedUsers set, any authenticated read-only user can invoke set_server_setting to modify server GlobalConfiguration, enabling configuration tampering or denial of service. The issue is fixed in 26.8.1.
CVE-2026-75845
Score 6.3 from GitHub Security Advisory published 2026-08-18. a secondary CVSS source baseline 6.3; sources differ by 0.0.
- 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.3
- EG Score
- 6.3(high)
- EG Risk
- 44(Track)EG Risk 44/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 computedSeverity63% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 18, 2026
Advisory Details (2)
Auto-updated Aug 18, 2026ArcadeDB 26.4.2 before 26.8.1 Authorization Bypass via set_server_setting | Advisories | VulnCheck
https://www.vulncheck.com/advisories/arcadedb-before-authorization-bypass-via-set-server-settingAuthorization bypass in ArcadeDB MCP: read-only user can invoke server-admin set_server_setting · Advisory · ArcadeData/arcadedb · GitHub
https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-pff6-hp53-pj54Vendor Advisories for CVE-2026-75845(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× 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-08-20 22:56 UTCEPSS rescore
- 2026-08-20 16:26 UTCEG score recompute
- 2026-08-20 16:26 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 15:56 UTCEG score recompute
- 2026-08-19 15:56 UTCGHSA enrichment
- 2026-08-18 15:22 UTCEG score recompute
- 2026-08-18 15:21 UTCGHSA enrichment
- 2026-08-18 15:15 UTCEG score recompute
- 2026-08-18 15:15 UTCGHSA enrichment
- 2026-08-18 12:34 UTCEG score recompute
- 2026-08-18 12:34 UTCGHSA enrichment
- 2026-08-18 11:29 UTCEG score recompute
- 2026-08-18 11:29 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-269
Frequently asked(5)
What is CVE-2026-75845?
When was CVE-2026-75845 disclosed?
Is CVE-2026-75845 actively exploited?
What is the CVSS score of CVE-2026-75845?
How do I remediate CVE-2026-75845?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75845
Is Your Infrastructure Affected by CVE-2026-75845?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.