CVE-2026-58485

mcp-searxng: DNS-resolved Private Hostname SSRF in `web_url_read`

Published Sep 15, 2026 CVSS 3.1 · 7.1 High EPSS < 1% KEV · Not listed
Description
mcp-searxng is a Model Context Protocol server that gives AI assistants web search and URL-reading capabilities through SearXNG. Prior to 1.7.1, web_url_read receives its caller-controlled URL through src/index.ts and validates only the literal hostname in assertUrlAllowed() within src/url-reader.ts before undiciFetch() performs operating-system DNS resolution. A public-looking attacker-controlled hostname that resolves to a private, loopback, link-local, or cloud-metadata address therefore passes the lexical check and causes the MCP server to connect to the internal destination. In the default HTTP configuration, an unauthenticated network client can use this path to read internal services, expose credentials or service tokens, and enumerate reachable internal hosts; in STDIO deployments, prompt-influenced tool selection can provide the malicious URL. Direct private IP literals are blocked, and MCP_HTTP_ALLOW_PRIVATE_URLS remains an explicit opt-out. This issue is fixed in version 1.7.1.

Analysis

AI-generated

Technical impact

An input validation flaw in the web_url_read endpoint allows an attacker to supply a hostname that resolves to a private, loopback, link‑local, or cloud‑metadata address. Because the server performs DNS resolution after only a lexical hostname check, the attacker can make the server reach internal services, potentially exfiltrating credentials, enumerating hosts, or reading protected data. The flaw does not require authentication in the default HTTP configuration, making it accessible to unauthenticated network clients.

Affected Systems

The vulnerable releases belong to the ihor‑sokoliuk mcp‑searxng project. Any version released before 1.7.1 is affected. Version 1.7.1 and later contain the fix that blocks such untrusted DNS resolutions.

Risk and Exploitability

The CVSS score is 7.1, indicating a high severity. The EPSS score is less than 1% (0.00135), indicating a very low but non‑zero probability of exploitation, and the vulnerability is not listed in the CISA KEV catalog, but the attack vector—unauthenticated network access to an HTTP endpoint—remains feasible. An attacker can leverage the flaw to read internal resources or leak service tokens; the risk is therefore significant for environments where the MCP server is exposed to untrusted networks.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the mcp‑searxng package to version 1.7.1 or later to apply the address‑validation fix.
  • Configure the web_url_read API to require authentication or restrict it to trusted clients only.
  • Deploy network controls to block outbound connections from the MCP server to internal IP ranges that should not be reachable from the public interface.

Generated by OpenCVE AI on September 20, 2026 at 14:32 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Ihor-sokoliuk
Ihor-sokoliuk mcp-searxng
Vendors & Products Ihor-sokoliuk
Ihor-sokoliuk mcp-searxng
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description mcp-searxng is a Model Context Protocol server that gives AI assistants web search and URL-reading capabilities through SearXNG. Prior to 1.7.1, web_url_read receives its caller-controlled URL through src/index.ts and validates only the literal hostname in assertUrlAllowed() within src/url-reader.ts before undiciFetch() performs operating-system DNS resolution. A public-looking attacker-controlled hostname that resolves to a private, loopback, link-local, or cloud-metadata address therefore passes the lexical check and causes the MCP server to connect to the internal destination. In the default HTTP configuration, an unauthenticated network client can use this path to read internal services, expose credentials or service tokens, and enumerate reachable internal hosts; in STDIO deployments, prompt-influenced tool selection can provide the malicious URL. Direct private IP literals are blocked, and MCP_HTTP_ALLOW_PRIVATE_URLS remains an explicit opt-out. This issue is fixed in version 1.7.1.
Title mcp-searxng: DNS-resolved Private Hostname SSRF in `web_url_read`
Weaknesses CWE-918
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N'}

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Sep 15, 2026, 6:31 PM
Reserved
Jun 30, 2026, 8:21 PM
Status
Deferred
Published
Sep 15, 2026, 6:17 PM
Modified
Sep 30, 2026, 5:51 PM