ArcadeData ArcadeDB MCP database name enumeration in resolveDatabase
- Exploited
- No known exploitation
- Fix
- Fixed in 26.11.1
- Who is exposed
- Specific setups only
Summary
ArcadeDB 26.2.1 before 26.11.1 contains an observable response discrepancy in MCPToolUtils.resolveDatabase, which checks database existence before authorization and returns distinct 'not authorized' and 'does not exist' errors; separately, a failed Bolt LOGON from READY leaves the previous principal bound after RESET. Authenticated MCP callers can enumerate names of databases they are not granted by probing tools such as query or get_schema.
Who should check
Teams running the ArcadeDB arcadedb-mcp module (com.arcadedb:arcadedb-mcp) up to 26.10.2 that let authenticated callers use MCP tools
“com.arcadedb:arcadedb-mcp”
What to do
Check whether your setup matches what the bug needs.
ArcadeDB 26.2.1 up to 26.10.2 (fixed in 26.11.1) The MCP server is in use and the caller is authenticated and allowed onto the MCP surface Bolt listener: a LOGON from READY fails, then RESET restores the previous principal (separate item)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-134329 (ArcadeDB 26.2.1 before 26.11.1 Database Enumeration via MCP Tools and Bolt LOGON Flaw), 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-134329 (entry last updated 2026-11-21):
Affected:
- Maven package com.arcadedb:arcadedb-mcp: from 26.2.1, fixed in 26.11.1
Fixed versions: 26.11.1.
Conditions (all must be true for the bug to be hit):
- ArcadeDB 26.2.1 up to 26.10.2 (fixed in 26.11.1) (source: https://www.vulncheck.com/advisories/arcadedb-26.2.1-before-26.11.1-database-enumeration-via-mcp-tools-and-bolt-logon-flaw)
- The MCP server is in use and the caller is authenticated and allowed onto the MCP surface (source: https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-34v6-3chg-hcjq)
- Bolt listener: a LOGON from READY fails, then RESET restores the previous principal (separate item) (source: https://www.vulncheck.com/advisories/arcadedb-26.2.1-before-26.11.1-database-enumeration-via-mcp-tools-and-bolt-logon-flaw)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134329 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134329 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-34v6-3chg-hcjq
- https://www.vulncheck.com/advisories/arcadedb-26.2.1-before-26.11.1-database-enumeration-via-mcp-tools-and-bolt-logon-flaw
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-134329
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-134329"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Maven packages
- Severity7.1/10CVSS 7.1
- 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
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · ArcadeData/arcadedb · Advisory GHSA-34v6-3chg-hcjq |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134329 |
| Record | NVD · CVE-2026-134329 |
| Other links 1 | |
| Link | vulncheck.com · advisories/arcadedb-26.2.1-before-26.11.1-database-enumeration-via-mcp-tools-and-bolt-logon-flaw |
Questions about CVE-2026-134329
Is CVE-2026-134329 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?
An authenticated MCP caller can learn the names of databases it has not been granted access to, by probing MCP tools one name at a time. The advisory also describes a separate Bolt LOGON flaw, where a failed LOGON from READY leaves the previous principal bound after RESET.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134329?
com.arcadedb:arcadedb-mcp (Maven): from 26.2.1 before 26.11.1.
Source: cve.now feed data
Am I affected, and how do I check?
ArcadeDB 26.2.1 up to 26.10.2 is affected when the MCP server is in use and the caller is authenticated and allowed onto the MCP surface. The Bolt LOGON condition is listed as a separate item in the advisory, so check your Bolt listener setup as well.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134329?
Upgrade ArcadeDB to 26.11.1, which is the fixed version.
Source: vulncheck.com, github.com
Related
- CVE-2026-134324ArcadeDB 26.3.1 before 26.11.1 MCP Read-Only Bypass via Gremlin Groovy Analysis
- CVE-2026-134325ArcadeDB before 26.11.1 Unauthenticated Redis Connection Hold Denial of Service
- CVE-2026-134337ArcadeDB 26.8.1 before 26.11.1 Native-Image Read-Only Bypass via Nested SELECT Writes
- CVE-2026-134338ArcadeDB 25.8.1 before 26.11.1 Per-Type ACL Bypass via ALTER TYPE Rename
- CVE-2026-134339ArcadeDB from 26.11.1-SNAPSHOT before 26.11.1 Authorization Bypass via Batch Endpoint
- CVE-2026-93593ArcadeDB before 26.9.1 TimeSeries ACL Bypass via Type Permission
No corrections so far. Something wrong on this page? Report an error.