# CVE-2026-67343: ArcadeDB before 26.7.2 Cluster Token Disclosure via GET /api/v1/server

> Authenticated users can retrieve the cluster token from the server API, enabling root impersonation and administrative control over the database.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-3cc2-w6p6-c4vg, GHSA-46hj-24h4-j8gf

## What is CVE-2026-67343?

CVE-2026-67343 is a high-severity vulnerability in ArcadeData arcadedb, published on 1 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-67343?


## How do I fix CVE-2026-67343?

No fix has been published for CVE-2026-67343 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-67343 being exploited?

There is no known exploitation of CVE-2026-67343 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-67343 and fix it if it is affected.

What it is: CVE-2026-67343 is a high-severity vulnerability in ArcadeData arcadedb, published on 1 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-67343 in the wild and no public exploit code.

Affected product: ArcadeData arcadedb. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-67343/ (Markdown: https://insights.sbomify.com/CVE-2026-67343/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-67343
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-67343
- OSV: https://osv.dev/vulnerability/CVE-2026-67343

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-67343/
Summaries are generated and may contain mistakes; the official description above is the record.