# CVE-2026-72860: Server-side request forgery in 9router

> Attackers can bypass SSRF protections to access internal network resources and read sensitive data via IPv4-mapped IPv6 address manipulation.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/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:** 20 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-cqgh-7h49-q3mr

## What is CVE-2026-72860?

CVE-2026-72860 is a medium-severity server-side request forgery vulnerability in decolua 9router, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The POST /api/provider-nodes/validate route in 9router takes a caller-supplied baseUrl and issues server-side HTTP requests to it, guarding the destination with assertPublicUrl from src/shared/utils/ssrfGuard.js. That guard compares hostname strings only: it resolves no DNS, does not revalidate after a redirect, and its IPv4-mapped IPv6 branch is unreachable. The branch matches ^::ffff:(\d+\.\d+\.\d+\.\d+)$, but the WHATWG URL parser canonicalizes such literals to hextets before the guard runs, so new URL("http://[::ffff:127.0.0.1]/").hostname yields [::ffff:7f00:1] and the pattern is tested against a string it is never handed. Every IPv4-mapped address therefore passes, and http://[::ffff:7f00:1] and http://[::ffff:a9fe:a9fe] reach loopback and link-local metadata addresses; a hostname whose A record points at an internal address passes as well because no resolution occurs. In the custom-embedding branch the upstream response body is truncated to 200 bytes and returned to the caller whenever the upstream status is neither 2xx nor 401 nor 403, which discloses the beginning of internal responses, and the other validation types remain usable for blind internal port scanning through status and timing differences. The caller-supplied apiKey is forwarded to the internal destination as an Authorization Bearer header. A dashboard session is required by default, and none is required when requireLogin is disabled.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-184 (Incomplete List of Disallowed Inputs)

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


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

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

## Is CVE-2026-72860 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72860 is a medium-severity server-side request forgery vulnerability in decolua 9router, published on 20 Aug 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-72860 exists.

Affected product: decolua 9router. 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-72860/ (Markdown: https://insights.sbomify.com/CVE-2026-72860/index.md)
```

## Sources

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

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