CVE-2026-75839: ArcadeDB before 26.8.1 Information Disclosure via Cluster Endpoints
ArcadeDB (com.arcadedb:arcadedb-server) versions <= 26.7.3 contain an insecure direct object reference (IDOR) vulnerability in the Raft cluster-info endpoints (GetClusterHandler and PostBootstrapStateHandler), which authenticate but do not authorize access. On an ArcadeDB HA cluster (only reachable when arcadedb.ha.enabled is set and the ha-raft module is loaded), any authenticated user — including one granted access to only one database or none — can enumerate the full server database registry and retrieve per-database metadata such as database names, last transaction IDs, bootstrap fingerprints, and peer/leader cluster topology, resulting in cross-database information disclosure. Fixed in 26.8.1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
com.arcadedb:arcadedb-serverto a version that resolves this vulnerability.Fixed in 26.8.1 - Configuration
Set arcadedb.ha.enabled to false to prevent access to the Raft cluster-info endpoints when the ha-raft module is loaded.
ArcadeDB HA arcadedb.ha.enabled = false - Compensating control
Ensure the ArcadeDB HA cluster endpoints (Raft cluster-info) are not reachable from untrusted networks; restrict access to trusted clients only while upgrading.
Event History
Frequently Asked Questions
Which deployments are exposed?
Exposure requires an ArcadeDB HA cluster with arcadedb.ha.enabled set and the ha-raft module loaded. The affected cluster-info endpoints are not reachable in deployments that do not meet those conditions.
What access does an attacker need?
An attacker needs valid authentication, but no authorization to the targeted databases. A user limited to one database, or even a user with no database access, can retrieve cluster-wide database registry and topology metadata.
What should be done if patching cannot happen immediately?
Upgrade ArcadeDB to version 26.8.1, which fixes the issue. If upgrading is not immediately possible, restrict access to the affected HA cluster endpoints to trusted authenticated users and avoid granting authentication to users who do not require cluster-level visibility.