# CVE-2026-93597: ArcadeDB before 26.9.1 SSRF via IPv6 transition addresses

> Authenticated attackers can bypass SSRF protections using IPv6 transition addresses to access internal services and cloud metadata in ArcadeDB.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L`)
- **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:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-67m7-7w7g-mpmh, GHSA-9fpr-24pp-pfx2

## What is CVE-2026-93597?

CVE-2026-93597 is a medium-severity server-side request forgery vulnerability in ArcadeData arcadedb, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ArcadeDB versions before 26.9.1 fail to validate IPv6 transition addresses in the SSRF guard used by IMPORT DATABASE and server commands. Authenticated attackers can supply URLs resolving to NAT64, 6to4, or Teredo addresses embedding RFC 1918 or loopback IPv4 payloads to reach internal services and cloud metadata endpoints.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-93597 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93597 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93597 is a medium-severity server-side request forgery vulnerability in ArcadeData arcadedb, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93597 exists.

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-93597/ (Markdown: https://insights.sbomify.com/CVE-2026-93597/index.md)
```

## Sources

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

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