CVE-2026-93596
MEDIUMDescription
ArcadeDB before 26.9.1 (com.arcadedb:arcadedb-engine <= 26.8.1) fails to bind the authenticated principal onto the DatabaseAsyncTransaction async worker threads used by the parallel edge-connect phase of POST /api/v1/batch/{database}. Because those workers have no current user, LocalDatabase.checkPermissionsOnFile returns early and allows the write, bypassing per-type CREATE_RECORD/UPDATE_RECORD ACL enforcement. In deployments that rely on per-type or per-group ACLs, an authenticated low-privilege user holding CREATE_RECORD on an edge type E but with CREATE_RECORD/UPDATE_RECORD revoked on a vertex type V can submit a graph edge-load batch request (with parallelFlush at its default value of true) and durably append edges to protected vertices of type V by writing records into V's <V>_out_edges/<V>_in_edges buckets, resulting in unauthorized modification of graph adjacency. Setting parallelFlush=false causes the request to be correctly rejected. This is an incomplete fix of GHSA-c23x-pqcj-7hfm, which bound the principal only on the HTTP handler thread.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Exploit Intelligence
EPSS data unavailable for this CVE.
References
Related Vulnerabilities
Other CWE-862 (Missing Authorization) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2021-39226 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2022-0543 | Critical | 10.0 | 99% | KEV | Fix |
| CVE-2021-21978 | Critical | 9.8 | 99% | - | Fix |
| CVE-2023-52163 | High | 8.8 | 97% | KEV | - |
| CVE-2022-1329 | High | 8.8 | 93% | - | - |
| CVE-2023-6875 | Critical | 9.8 | 90% | - | - |
Common questions
How do I fix CVE-2026-93596?
No published fix for CVE-2026-93596 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
How severe is CVE-2026-93596?
CVE-2026-93596 has a CVSS v3 base score of 4.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-93596
Markdown
[](https://tridentstack.com/cve/CVE-2026-93596)HTML
<a href="https://tridentstack.com/cve/CVE-2026-93596"><img src="https://tridentstack.com/cve/badge/CVE-2026-93596.svg" alt="CVE-2026-93596"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-18.