# CVE-2026-67357: ArcadeDB before 26.7.3 Information Disclosure via get_server_settings

> Attackers with MCP access can retrieve the cluster token to impersonate root and compromise the ArcadeDB server.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:H/AT:P/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:** 2 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-7qj8-rw8h-hhxv, GHSA-p9wc-4fhr-78wm

## What is CVE-2026-67357?

CVE-2026-67357 is a high-severity vulnerability in ArcadeData arcadedb, published on 2 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.3 contain an information disclosure vulnerability in the MCP get_server_settings tool that leaks the arcadedb.ha.clusterToken in cleartext. Attackers with MCP access can retrieve the cluster token and use it with X-ArcadeDB-Cluster-Token and X-ArcadeDB-Forwarded-User headers to impersonate root and achieve full server compromise.

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

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


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

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

## Is CVE-2026-67357 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67357 is a high-severity vulnerability in ArcadeData arcadedb, published on 2 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-67357 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-67357/ (Markdown: https://insights.sbomify.com/CVE-2026-67357/index.md)
```

## Sources

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

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