CVE-2026-63313

Received Received - Intake

SSRF in 9Router via Unvalidated URL Parameter

Publication date: 2026-07-23

Last updated on: 2026-07-23

Assigner: VulnCheck

Description

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-23

Last Modified

2026-07-23

Generated

2026-07-24

AI Q&A

2026-07-24

EPSS Evaluated

N/A

NVD

CVE-2026-63313

Affected Vendors & Products

Vendor	Product	Version / Range
9router	9router	to 0.4.72 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-918	The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

Executive Summary

9Router before version 0.4.72 has a server-side request forgery (SSRF) vulnerability in the /v1/web/fetch endpoint. This endpoint accepts a user-controlled URL parameter and forwards it to an external scraping service without proper validation. The URL is only checked for basic syntax, allowing access to internal services, cloud metadata endpoints, and private IP ranges.

Detection Guidance

To detect this SSRF vulnerability in 9Router, monitor network traffic for outbound requests to private IP ranges, cloud metadata endpoints (e.g., 169.254.169.254), or internal hostnames originating from the 9Router service. Check logs for requests to the /v1/web/fetch endpoint with suspicious URLs.

Impact Analysis

An attacker with authenticated or local access could exploit this to read internal service responses, access cloud metadata credentials, or interact with localhost endpoints. This could lead to data breaches, unauthorized access to sensitive systems, or bypassing authentication mechanisms.

Compliance Impact

This SSRF vulnerability could result in unauthorized access to sensitive data, violating confidentiality requirements under GDPR and HIPAA. Exposure of cloud metadata or internal services may lead to non-compliance with data protection and security standards.

Mitigation Strategies

Immediately update 9Router to version 0.4.72 or later to patch the SSRF vulnerability. If an update is not available, restrict access to the /v1/web/fetch endpoint and block outbound requests to private IP ranges, cloud metadata endpoints, and internal hostnames via firewall rules.

Hi! I’m here to help you understand CVE-2026-63313. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70