Root impersonation via exposed HA cluster token
Published Aug 1, 2026 · Updated Aug 1, 2026
Information disclosure in ArcadeDB before 26.7.2 allows remote authenticated users to obtain a configured HA cluster token. The GET /api/v1/server handler exports non-database settings but masks only names containing password, ignoring the hidden-setting flag on arcadedb.ha.clusterToken. Exploitation requires an explicitly configured HA_CLUSTER_TOKEN; replay with the forwarded-user header grants root administrative control, including database changes and server shutdown.
Summary
What happened
Information disclosure in ArcadeDB before 26.7.2 allows remote authenticated users to obtain a configured HA cluster token. The GET /api/v1/server handler exports non-database settings but masks only names containing password, ignoring the hidden-setting flag on arcadedb.ha.clusterToken. Exploitation requires an explicitly configured HA_CLUSTER_TOKEN; replay with the forwarded-user header grants root administrative control, including database changes and server shutdown.
The record
- CVE
- CVE-2026-67343
- Published
- Aug 1, 2026
- Updated
- Aug 1, 2026
- Vendor
- Arcade Data
- Product
- ArcadeDB
- Classifications
- CWE-200, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 1, 2026CVE publishedPublication date reported by the CVE source.
- Aug 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <26.7.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor advisory exploit procedureproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo