Quick answers
- Is CVE-2026-63313 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63313 being exploited in the wild.
- How severe is CVE-2026-63313?
- High severity, with a CVSS score of 7.7, published 23 July 2026.
- Which products and versions are affected?
- decolua 9router < 0.4.72.
- Is there a fix for CVE-2026-63313?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-63313 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-63313?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in the /v1/web/fetch endpoint of 9Router due to insufficient validation of the 'url' parameter. The application uses 'new URL()' to check syntax but fails to implement a blocklist for private IP ranges (RFC 1918), loopback addresses, or cloud metadata services (e.g., 169.254.169.254). An authenticated attacker can provide an internal URL which the server then fetches via configured scraping providers (Firecrawl, Jina, etc.), returning the response content to the attacker. This enables read-access SSRF, potentially leading to the theft of IAM credentials from cloud metadata endpoints or the bypass of authentication on localhost services. The issue is patched in version 0.4.72.
Affected products
- decolua 9router < 0.4.72
Timeline
- 2026-07-03: advisory: GitHub Security Advisory published by vendor
- 2026-07-23: disclosed: CVE published to NVD