CVE-2026-114058
Deferred Deferred - Pending Action

ArcadeDB Missing Authorization in Bolt Protocol Handler

Vulnerability report for CVE-2026-114058, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-21

Last updated on: 2026-10-27

Assigner: VulnCheck

Description

ArcadeDB from 26.2.1 before 26.10.1 contains a missing authorization vulnerability in the Bolt protocol handler that lets authenticated users read other databases' schema metadata. Attackers with credentials for one database can set the db field in RUN or BEGIN messages and call db.labels() or SHOW INDEXES to enumerate unauthorized schemas.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-21
Last Modified
2026-10-27
Generated
2026-11-10
AI Q&A
2026-10-22
EPSS Evaluated
2026-11-09
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
ArcadeData arcadedb 26.2.1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in ArcadeDB (CVE-2026-114058) is a missing authorization flaw in the Bolt protocol handler. It allows authenticated users with access to one database to read schema metadata from other databases on the same server without proper authorization. The issue occurs because the Bolt protocol handler does not enforce per-database authorization checks when switching databases.

Detection Guidance

To detect this vulnerability, monitor network traffic on the default Bolt port (7687) for suspicious RUN or BEGIN messages with modified db fields. Check ArcadeDB logs for unauthorized schema metadata access attempts like db.labels() or SHOW INDEXES calls. Use packet inspection tools like Wireshark to filter for Bolt protocol traffic and verify if users are querying schemas outside their authorized databases.

Impact Analysis

An attacker with valid credentials for one database could exploit this to enumerate schema metadata from other databases, including node/relationship types, property keys, and index definitions. While actual record data remains protected, the exposed schema details could help attackers plan further exploits or reconnaissance.

Compliance Impact

This vulnerability exposes database schema metadata, which could indirectly impact compliance by revealing system structure details that might aid in further attacks. However, the actual record data remains protected, limiting direct regulatory violations. GDPR and HIPAA focus on unauthorized data access; since no records are exposed, the primary risk is secondary exploitation rather than direct non-compliance.

Mitigation Strategies

Restrict network access to the Bolt port (7687) by binding it to trusted IPs or using firewalls. Temporarily disable the Bolt protocol if not required. Monitor for unauthorized schema queries and update ArcadeDB to a patched version once available. Review user permissions to ensure least privilege access across databases.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-114058. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...