Skip to main content
Menu
CVEs

ArcadeData ArcadeDB Gremlin read-only bypass in Gremlin Groovy query analysis

Only affects ArcadeDB 26.3.1 up to 26.11.1 when Gremlin scripts run on the auto or groovy engine, and only for server administrators. Fixed in 26.11.1.

CVE-2026-134324Published November 21, 2026, updated

6.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 26.11.1
Who is exposed
Specific setups only

Summary

Written by a model

ArcadeDB 26.3.1 before 26.11.1 contains a read-only bypass vulnerability that allows server administrators to commit writes through the MCP read-only query tool by submitting Groovy-fallback Gremlin scripts. GremlinQueryEngine.analyze() evaluates scripts like Graph API addVertex calls on the auto or groovy engine and classifies them as READ, persisting writes the read-only restriction should refuse.

Who should check

Teams running ArcadeDB 26.3.1 through 26.10.2 with the MCP server, where a root or server-administrator user uses Gremlin on the auto or groovy engine; Maven users of com.arcadedb:arcadedb-gremlin.

“ArcadeDB 26.3.1 before 26.11.1 contains a read-only bypass vulnerability”

vulncheck.com

What to do

  1. Check whether your setup matches what the bug needs.

    Gremlin script runs on the auto or groovy engine, so the Groovy fallback evaluates it during analysis. The write is committed through the MCP read-only query tool, which runs analyze() before refusing. The caller must be a server administrator; a non-administrator is refused. Affected versions are ArcadeDB 26.3.1 up to but not including 26.11.1.
  2. Upgrade to a fixed version: 26.11.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134324 (ArcadeDB 26.3.1 before 26.11.1 MCP Read-Only Bypass via Gremlin Groovy Analysis), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134324 (entry last updated 2026-11-21):
Affected:
- Maven package com.arcadedb:arcadedb-gremlin: from 26.3.1, fixed in 26.11.1
- Maven package com.arcadedb:arcadedb-mcp: from 26.3.1, fixed in 26.11.1
Fixed versions: 26.11.1.
Conditions (all must be true for the bug to be hit):
- Gremlin script runs on the auto or groovy engine, so the Groovy fallback evaluates it during analysis. (source: https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-r946-225c-5x88)
- The write is committed through the MCP read-only query tool, which runs analyze() before refusing. (source: https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-r946-225c-5x88)
- The caller must be a server administrator; a non-administrator is refused. (source: https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-r946-225c-5x88)
- Affected versions are ArcadeDB 26.3.1 up to but not including 26.11.1. (source: https://www.vulncheck.com/advisories/arcadedb-26.3.1-before-26.11.1-mcp-read-only-bypass-via-gremlin-groovy-analysis)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-134324 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134324 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Maven): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-r946-225c-5x88
- https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-6jr9-6vw5-xjf6
- https://www.vulncheck.com/advisories/arcadedb-26.3.1-before-26.11.1-mcp-read-only-bypass-via-gremlin-groovy-analysis
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134324
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134324"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Maven packages
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 32 if CISA's SSVC rates it automatable

Impact

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 5

Questions about CVE-2026-134324

Is CVE-2026-134324 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

Gremlin scripts on the auto or groovy engine are evaluated by the Groovy fallback during analysis, which writes through the Graph API. The MCP read-only query tool runs analyze() before refusing, so the write is committed and reported as a read.

Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-134324?

com.arcadedb:arcadedb-gremlin (Maven): from 26.3.1 before 26.11.1. com.arcadedb:arcadedb-mcp (Maven): from 26.3.1 before 26.11.1.

Source: cve.now feed data

Am I affected, and how do I check?

Affected versions are ArcadeDB 26.3.1 up to but not including 26.11.1. The setup is Gremlin scripts on the auto or groovy engine submitted by a server administrator (the root user); non-administrators are refused. Check the installed version against that range and the engine used for Gremlin scripts.

Source: github.com, vulncheck.com

How do I fix CVE-2026-134324?

Upgrade to ArcadeDB 26.11.1, which is the fixed version.

Source: github.com, vulncheck.com

No corrections so far. Something wrong on this page? Report an error.