Skip to main content
CVE-2026-134329VulnerabilityPublished

ArcadeDB 26.2.1 before 26.11.1 contains an observable response discrepancy in MCPToolUtils.resolveDatabase, which

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-134329· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 26.11.1 soon.

Data as of 21 Nov 2026, 19:45 UTC

CVSS 4.0 base score
7.1High
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.07.1
CNA (VulnCheck)CVSS 3.14.3
Patch
Available – fixed in 26.11.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/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.2.1 <26.11.1
Fixed in
  • 26.11.1
Mavenarcadedbpkg:maven/arcadedbOther threatsAffected
  • >=26.2.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

If you cannot patch yet, restrict MCP access to trusted users only to limit potential enumeration.

Description

ArcadeDB versions from 26.2.1 up to but not including 26.11.1 have a vulnerability where the MCPToolUtils.resolveDatabase method reveals whether a database exists before authorization, returning different errors for 'not authorized' versus 'does not exist'. Additionally, a failed Bolt LOGON command leaves the previous principal bound after a RESET. This allows authenticated MCP users to enumerate database names they are not authorized to access by probing with certain tools.

References

Community reviews

Loading reviews…