ArcadeDB before 26.8.1 fails to bind the authenticated principal (setCurrentUser) on its batch and time-series HTTP handlers. Because no principal is bound on the worker thread, the engine's fine-grained per-type ACL layer (LocalBucket.checkPermissionsOnFile) does not execute for these handlers. In deployments that use per-type or per-group ACLs, a user with database access but only limited per-type permissions can read from and write to types they are not authorized to access by submitting requests to the batch/time-series endpoints. Deployments that rely solely on database-level access control are not affected.
CVE-2026-75850
Score 4.2 from GitHub Security Advisory (severity: LOW) published 2026-08-18. a secondary CVSS source baseline 4.2; 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
- 4.2
- EG Score
- 4.2(high)
- EG Risk
- 19(Track)EG Risk 19/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 computedSeverity42% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 6%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 19, 2026
Advisory Details (2)
Auto-updated Aug 18, 2026ArcadeDB before 26.8.1 Per-Type ACL Bypass via Batch Handlers | Advisories | VulnCheck
https://www.vulncheck.com/advisories/arcadedb-before-per-type-acl-bypass-via-batch-handlersBatch/time-series HTTP handlers skip per-type ACL enforcement because no principal is bound · Advisory · ArcadeData/arcadedb · GitHub
https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-c23x-pqcj-7hfmVendor Advisories for CVE-2026-75850(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 13× in last 7d / 13× 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 14:01 UTCEG score recompute
- 2026-08-20 14:01 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 15:25 UTCEG score recompute
- 2026-08-19 15:25 UTCGHSA enrichment
- 2026-08-19 14:38 UTCEG score recompute
- 2026-08-19 14:38 UTCGHSA enrichment
- 2026-08-19 10:55 UTCGHSA enrichment
- 2026-08-18 12:33 UTCEG score recompute
- 2026-08-18 12:33 UTCGHSA enrichment
- 2026-08-18 11:29 UTCEG score recompute
- 2026-08-18 11:29 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-75850?
When was CVE-2026-75850 disclosed?
Is CVE-2026-75850 actively exploited?
What is the CVSS score of CVE-2026-75850?
How do I remediate CVE-2026-75850?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75850
Is Your Infrastructure Affected by CVE-2026-75850?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.