CVE-2026-63313

HIGHPre-NVD 7.77.7—
EchelonGraph scoreHIGH confidence

Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-07-24. a secondary CVSS source baseline 7.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.7Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

9Router before 0.4.72 contains a server-side request forgery (SSRF) vulnerability in the /v1/web/fetch endpoint. The endpoint accepts a user-controlled url parameter and passes it to a configured external scraping provider (Firecrawl, Jina Reader, Tavily, or Exa) to fetch content. The URL is only validated as syntactically valid via new URL() with no blocklist for private IP ranges, cloud metadata endpoints (e.g., 169.254.169.254), link-local addresses, or internal hostnames. An authenticated or locally-connected user can cause the server to fetch arbitrary internal URLs and have the response content returned, enabling read-access SSRF that can expose cloud metadata credentials, reach internal services, and bypass authentication on localhost endpoints.

CVSS v3
7.7
EG Score
7.7(high)
EG Risk
51(Track)
EG Risk 51/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity77% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

July 23, 2026

Last Modified

July 24, 2026

Advisory Details (2)

Auto-updated Jul 23, 2026
Patch available. Sources: github.
generic

9Router before 0.4.72 Server-Side Request Forgery via /v1/web/fetch | Advisories | VulnCheck

https://www.vulncheck.com/advisories/9router-before-server-side-request-forgery-via-v1-web-fetch
github Patch Available

Server-Side Request Forgery (SSRF) via /v1/web/fetch Endpoint · Advisory · decolua/9router · GitHub

https://github.com/decolua/9router/security/advisories/GHSA-qj3v-64wj-q825

Vendor Advisories for CVE-2026-63313(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 02:09 UTCEG score recompute
  2. 2026-07-27 02:09 UTCGHSA enrichment
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 14:37 UTCEG score recompute
  6. 2026-07-26 14:37 UTCGHSA enrichment
  7. 2026-07-26 03:06 UTCEG score recompute
  8. 2026-07-26 03:06 UTCGHSA enrichment
  9. 2026-07-25 14:18 UTCEPSS rescore
  10. 2026-07-25 14:18 UTCEPSS rescore
  11. 2026-07-24 14:18 UTCEPSS rescore
  12. 2026-07-24 14:18 UTCEPSS rescore
  13. 2026-07-23 21:37 UTCEG score recompute
  14. 2026-07-23 21:36 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-63313?
CVE-2026-63313 is a high vulnerability published on July 23, 2026. 9Router before 0.4.72 contains a server-side request forgery (SSRF) vulnerability in the /v1/web/fetch endpoint. The endpoint accepts a user-controlled url parameter and passes it to a configured external scraping provider (Firecrawl, Jina Reader, Tavily, or Exa) to fetch content. The URL is only…
When was CVE-2026-63313 disclosed?
CVE-2026-63313 was first published in the National Vulnerability Database on July 23, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63313 actively exploited?
CVE-2026-63313 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.9% of all scored CVEs.
What is the CVSS score of CVE-2026-63313?
CVE-2026-63313 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-63313?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63313, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-63313

Explore →

Is Your Infrastructure Affected by CVE-2026-63313?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs