Description
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.
Published: 2026-08-18
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

ArcadeDB versions up to 26.7.3 have an insecure direct object reference in the Raft cluster‑information endpoints. The endpoints authenticate requests but do not enforce authorization, which means any authenticated user, even one with access to only a single database or no databases, can enumerate the full database registry and retrieve sensitive metadata such as database names, last transaction IDs, bootstrap fingerprints, and cluster topology. The vulnerability can lead to cross‑database information disclosure, compromising confidentiality of cluster configuration data. It is classified as CWE‑200.

Affected Systems

The affected products are ArcadeData ArcadeDB versions 26.7.3 and earlier. The flaw is present only when the HA cluster configuration is enabled (arcadedb.ha.enabled set to true) and the ha‑raft module is loaded. Users deploying ArcadeDB in a high‑availability cluster environment should verify their version and configuration.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity. The EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog. The attack vector requires authentication, but any authenticated user can trigger the information disclosure, making the risk higher in environments where many users have valid credentials. An attacker could obtain cluster topology and database metadata, potentially facilitating further attacks such as privilege escalation or targeted exploits against specific databases. Because no elevation of privilege or code execution is involved, the primary risk is confidentiality exposure.

Generated by OpenCVE AI on August 18, 2026 at 13:05 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade ArcadeDB to version 26.8.1 or later where the IDOR has been fixed.
  • If HA clustering is not required, disable the feature by setting arcadedb.ha.enabled to false and removing the ha‑raft module from the deployment.
  • Apply network segmentation or firewall rules so that only trusted internal services can reach the cluster‑information endpoints, effectively limiting exposure to authenticated users.

Generated by OpenCVE AI on August 18, 2026 at 13:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 19 Aug 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 18 Aug 2026 13:00:00 +0000

Type Values Removed Values Added
First Time appeared Arcadedata
Arcadedata arcadedb
Vendors & Products Arcadedata
Arcadedata arcadedb

Tue, 18 Aug 2026 11:30:00 +0000

Type Values Removed Values Added
Description 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.
Title ArcadeDB before 26.8.1 Information Disclosure via Cluster Endpoints
Weaknesses CWE-200
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}

cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

Arcadedata Arcadedb
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-08-18T13:36:03.478Z

Reserved: 2026-08-18T10:59:33.701Z

Link: CVE-2026-75839

cve-icon Vulnrichment

Updated: 2026-08-18T12:51:14.261Z

cve-icon NVD

Status : Deferred

Published: 2026-08-18T12:19:34.180

Modified: 2026-08-31T20:33:07.713

Link: CVE-2026-75839

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-18T13:15:12Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor