Skip to main content
CVE-2026-134324VulnerabilityPublished

ArcadeDB 26.3.1 before 26.11.1 contains a read-only bypass vulnerability that allows server administrators to commit

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-134324· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium : upgrade to 26.11.1 when convenient.

Data as of 21 Nov 2026, 19:45 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.9
CNA (VulnCheck)CVSS 3.14.9
Patch
Available – fixed in 26.11.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade arcadedb to 26.11.1.

Affected software

ProductAffectedFixed in
ArcadeDataarcadedbAffected
  • >=26.3.1 <26.11.1
Fixed in
  • 26.11.1
Mavenarcadedbpkg:maven/arcadedbOther threatsAffected
  • >=26.3.1 <26.11.1
Fixed in
  • 26.11.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in ArcadeDB version 26.11.1 and later. Users should upgrade to version 26.11.1 or newer to remediate this vulnerability. No other mitigation steps are indicated.

Description

ArcadeDB versions from 26.3.1 up to but not including 26.11.1 contain a vulnerability that allows server administrators to bypass read-only restrictions in the MCP read-only query tool. This is achieved by submitting Groovy-fallback Gremlin scripts that perform write operations, which are incorrectly classified as read-only and thus allowed to persist. The vulnerability affects the GremlinQueryEngine.analyze() method, which fails to block these write operations in a read-only context.

References

Community reviews

Loading reviews…