CVE-2026-134329
ArcadeDB MCP errors disclosed database existence
ArcadeData · ArcadeDB · MCP tools and grouped Bolt session state
First documented disclosure · Review checkpoint
Summary
Different MCP errors disclosed whether an unauthorized database name existed; the same advisory also covers stale Bolt identity after failed reauthentication.
Severity and exploitation evidence
High · 7.1/10 · CVSS 4.0. Severity source.
Exploitation not established: The reviewed sources document a weakness or controlled demonstration; malicious exploitation against users is not established.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
MCP checked database existence before access. Separately, failed Bolt LOGON from READY preserved the old principal and RESET restored the connection state.
Conditions required
MCP: authenticated access to a tool and a candidate database name. Bolt: a previously authenticated connection reused without the normal LOGOFF sequence.
Potential impact
Database-name enumeration or continued use of the previous connection principal. The Bolt path grants no authority beyond that principal.
Affected versions and configurations
CNA: MCP package 26.2.1 before 26.11.1; original advisory lists through 26.10.2.
Fix and mitigation status
26.11.1, as stated in the original advisory and security release; tagged MCP resolution returns the same unknown-database result before opening unauthorized databases.
Practical next steps
Upgrade to 26.11.1. Reauthenticate pooled Bolt connections with the documented LOGOFF/LOGON sequence and do not transfer an authenticated connection between trust contexts.
Operating lesson
Authorize before exposing existence, and clear authentication state on failed transitions.
Evidence and limits
Original November 4; CNA November 21. VulnCheck CVSS 4.0 7.1 / 3.1 4.3 contrasts with the maintainer Low assessment. The official Neo4j driver sends LOGOFF and was a safe control; the stale-identity scenario concerns nonstandard clients/pools. MCP resources/read already used indistinguishable errors. The complete two-path advisory and stable release were reviewed; static tagged-source verification here covers the MCP guard, not a live Bolt reproduction.
Sources
- VulnCheck exact CVE authority record
Primary source ·
- ArcadeDB MCP/Bolt original advisory
Primary source ·
- ArcadeDB 26.11.1 security release
Primary source ·
- Tagged MCP database authorization ordering
Primary source ·