ArcadeDB's Gremlin wire-protocol plugin (com.arcadedb:arcadedb-gremlin) in versions <= 26.7.3 enforces authentication (SASL PLAIN) but performs no authorization: it never checks database access permissions (canAccessToDatabase) and never binds the authenticated principal into the engine. As a result, any valid server credential — even one provisioned for zero or one unrelated database — can read, write, and drop data in any database on the server by selecting a target database via a traversal-source alias, completely bypassing the engine's per-type/read-only/UPDATE_SCHEMA ACLs. The issue is fixed in version 26.8.1.
CVE-2026-75853
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-18. a secondary CVSS source baseline 8.8; sources differ by 0.0.
- 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
- 8.8
- EG Score
- 8.8(high)
- EG Risk
- 56(Track*)EG Risk 56/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 computedSeverity88% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 33%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 18, 2026
Advisory Details (2)
Auto-updated Aug 18, 2026ArcadeDB Gremlin Wire Protocol Authorization Bypass Cross-Database | Advisories | VulnCheck
https://www.vulncheck.com/advisories/arcadedb-gremlin-wire-protocol-authorization-bypass-cross-databaseGremlin wire protocol enforces authentication but no authorization, allowing cross-database read/write and engine ACL bypass · Advisory · ArcadeData/arcadedb · GitHub
https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-c287-v325-j5jxVendor Advisories for CVE-2026-75853(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 18× in last 7d / 18× 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-21 01:31 UTCEG score recompute
- 2026-08-21 01:31 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 14:01 UTCGHSA enrichment
- 2026-08-20 02:05 UTCEG score recompute
- 2026-08-20 02:05 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 14:34 UTCGHSA enrichment
- 2026-08-19 02:55 UTCEG score recompute
- 2026-08-19 02:54 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: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-75853?
When was CVE-2026-75853 disclosed?
Is CVE-2026-75853 actively exploited?
What is the CVSS score of CVE-2026-75853?
How do I remediate CVE-2026-75853?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75853
Is Your Infrastructure Affected by CVE-2026-75853?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.