Description
ArcadeDB versions before 26.7.2 fail to properly redact the cluster token in the GET /api/v1/server endpoint, allowing authenticated users to retrieve the arcadedb.ha.clusterToken value in cleartext. Attackers can use the leaked token with X-ArcadeDB-Cluster-Token and X-ArcadeDB-Forwarded-User headers to impersonate root and execute administrative actions including user creation, database operations, and server shutdown.
Published: 2026-08-01
Score: 8.7 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

ArcadeDB versions before 26.7.2 expose the cluster token through the GET /api/v1/server endpoint. The token is returned in clear text to any authenticated user. Attackers holding the token can send it in X-ArcadeDB-Cluster-Token and X-ArcadeDB-Forwarded-User headers to mimic a root session, allowing them to create or drop users, perform arbitrary database operations, and even shut down the server. This is a disclosure of sensitive information that leads to privilege escalation through the misuse of the cluster token.

Affected Systems

The affected product is ArcadeData’s ArcadeDB, an open‑source graph and document database. All releases prior to 26.7.2 are impacted, including 26.7.1 and earlier versions. The vulnerability is present in the API layer that serves the /api/v1/server resource.

Risk and Exploitability

The vulnerability carries a CVSS score of 8.7, indicating high severity. No EPSS score is available, and the issue is not in the CISA KEV catalog, suggesting no reported exploits yet. Exploitation requires valid authentication, but once an attacker obtains any authenticated session they can immediately retrieve the cluster token and abuse it. The risk is thus elevated in environments where the API is publicly reachable or where credential compromise is possible.

Generated by OpenCVE AI on August 3, 2026 at 09:36 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to ArcadeDB 26.7.2 or later to apply the fix that redacts the cluster token.
  • Restrict access to the /api/v1/server endpoint so that only trusted administrative users can call it, minimizing exposure.
  • Configure firewall rules to limit API access to trusted networks only.

Generated by OpenCVE AI on August 3, 2026 at 09:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 03 Aug 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

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


Sat, 01 Aug 2026 14:30:00 +0000

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

Sat, 01 Aug 2026 12:45:00 +0000

Type Values Removed Values Added
Description ArcadeDB versions before 26.7.2 fail to properly redact the cluster token in the GET /api/v1/server endpoint, allowing authenticated users to retrieve the arcadedb.ha.clusterToken value in cleartext. Attackers can use the leaked token with X-ArcadeDB-Cluster-Token and X-ArcadeDB-Forwarded-User headers to impersonate root and execute administrative actions including user creation, database operations, and server shutdown.
Title ArcadeDB before 26.7.2 Cluster Token Disclosure via GET /api/v1/server
Weaknesses CWE-200
References
Metrics cvssV3_1

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

cvssV4_0

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


Subscriptions

Arcadedata Arcadedb
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-08-03T19:38:25.856Z

Reserved: 2026-07-29T13:09:45.993Z

Link: CVE-2026-67343

cve-icon Vulnrichment

Updated: 2026-08-03T19:38:20.032Z

cve-icon NVD

Status : Received

Published: 2026-08-01T13:17:05.563

Modified: 2026-08-03T20:17:27.573

Link: CVE-2026-67343

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-03T09:45:04Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor