Quick answers
- Is CVE-2026-75851 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75851 being exploited in the wild.
- How severe is CVE-2026-75851?
- Critical severity, with a CVSS score of 9.9, published 18 August 2026.
- Which products and versions are affected?
- ArcadeData ArcadeDB 26.7.3 and earlier; fixed in 26.8.1.
- Is there a fix for CVE-2026-75851?
- A patch was published on 2026-08-18: Fix released in ArcadeDB 26.8.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-75851 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-75851?
- Check whether you run ArcadeData ArcadeDB at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a privilege escalation caused by improper propagation of authentication context in asynchronous command execution. When a user submits an HTTP POST to /api/v1/command with awaitResponse:false, the command is dispatched to an arcadedb-async-* worker thread whose DatabaseContext is never bound to the authenticated principal. The scripting authorization gate in PolyglotQueryEngine.command() explicitly returns early when no user is bound (a documented no-op), allowing JavaScript code to execute with unrestricted host access. An attacker with only read access to a single database can call database.getSecurity().createUser() to create an all-databases administrator account. Attack vector is network; low privilege (read-only database access) and low complexity required. The fix propagates the authenticated principal to async worker threads and calls setCurrentUser before command execution.
Affected products
- ArcadeData ArcadeDB 26.7.3 and earlier; fixed in 26.8.1
Timeline
- 2026-08-04: disclosed: GitHub Security Advisory published
- 2026-08-18: advisory: NVD entry published
- 2026-08-18: patched: Fix released in ArcadeDB 26.8.1