p PatchFirst

CVE-2026-58485

CVE-2026-58485 · mcp-searxng: DNS-resolved Private Hostname SSRF in `web_url_read`

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 7.1 · High · EPSS 0.2% · Fix available

Published
Updated

Stack: node

Affected products and versions

  • mcp-searxng

    Versions
    • < 1.7.1: Affected

    No fix published

  • mcp-searxng npm

    Affected ranges
    • SEMVER: < 1.7.1

    Update to 1.7.1

Original sources

Check your server →