CVE-2026-72860: Server-Side Request Forgery (SSRF) in decolua 9router
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.
CVSS v3.1
Score 8.5high
Affected software
decolua
9router
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The POST /api/provider-nodes/validate endpoint in 9router accepts a baseUrl parameter and makes server-side HTTP requests to it. The SSRF guard function assertPublicUrl only compares hostname strings without DNS resolution or redirect checks, and its IPv4-mapped IPv6 address handling is ineffective due to URL parser canonicalization. This allows requests to internal loopback and link-local addresses via IPv4-mapped IPv6 literals and hostnames resolving to internal IPs. The vulnerability also leaks up to 200 bytes of internal response bodies for certain HTTP statuses and allows blind internal port scanning through response status and timing differences. The apiKey from the caller is forwarded as an Authorization Bearer header to the internal target. Exploitation requires a dashboard session unless the requireLogin setting is disabled.
Potential Impact
An attacker with at least a dashboard session or with requireLogin disabled can exploit this SSRF vulnerability to make unauthorized HTTP requests to internal network resources, potentially accessing sensitive internal services. The vulnerability allows partial disclosure of internal response data and facilitates blind internal port scanning. The forwarding of the apiKey as an Authorization Bearer header to internal destinations could lead to unauthorized access or privilege escalation within internal services. The CVSS score of 8.5 reflects high impact with high confidentiality loss, limited integrity impact, and no availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to the dashboard and ensure requireLogin is enabled to prevent unauthenticated exploitation. Review and enhance SSRF protections to include DNS resolution, redirect validation, and proper handling of IPv4-mapped IPv6 addresses. Avoid forwarding sensitive credentials like apiKey to untrusted internal destinations.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-10T15:16:31.372Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a877790acd9273b492c5fcf
Added to database: 08/20/2026, 21:54:24 UTC
Last enriched: 09/25/2026, 02:39:53 UTC
Last updated: 10/05/2026, 06:48:18 UTC
Views: 79
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.