CVE-2026-63313
Authenticated SSRF in 9Router allows internal URL fetch and cloud metadata exposure.
Is CVE-2026-63313 being exploited?
Not confirmed. CVE-2026-63313 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.46% probability of exploitation in the next 30 days.
How severe is CVE-2026-63313?
CVE-2026-63313 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-63313?
Yes. A fix has been recorded for CVE-2026-63313. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-63313 affect?
CVE-2026-63313 affects 9Router < 0.4.72, /v1/web/fetch endpoint, Integrations: Firecrawl, Jina Reader, Tavily, Exa. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-63313?
Upgrade to 9Router 0.4.72; block private/metadata IPs and validate/whitelist URLs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated SSRF enables server-side requests to internal resources, exposing cloud metadata creds and accessing localhost/internal services.
Immediate action required
- affected< 0.4.72
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.