SearXNG MCP Server: Additional hardened-mode SSRF bypasses
CVE-2026-54689 · GHSA-wppf-h75h-6pm6 · published 2026-08-19
- Severity
- Medium
- CVSS score
- 6.3
- Chance of exploitation (EPSS)
- 0.19%
- Fixed in
- 1.2.1
- Exploitation Public proof of concept
- Automatable No
- Technical impact Partial
- CISA SSVC
This is a hardened-mode SSRF bypass. It represents an internal-only service reachable from the MCP server host. In real deployments, the same class of issue could allow weburlread to reach: local admin panels bound to loopback; Redis, Elasticsearch, or other local HTTP-like services; internal HTTP APIs on private networks; service mesh endpoints; cloud metadata endpoints, depending on routing and environment. This is especially relevant for MCP deployments because tool calls may be selected by an AI assistant. If untrusted content can influence tool use, it may be able to trigger weburlread with one of these bypass URLs.
Upgrade mcp-searxng to 1.2.1 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
A complete fix likely needs more than a connect-time DNS lookup guard. Suggested changes: Re-validate every redirect hop. One option is to use redirect: "manual" and apply the same URL policy to each Location before following it. Treat 0.0.0.0/8 and other IANA special-purpose ranges as internal/non-public. Handle IPv4-mapped IPv6 after canonicalization, including forms such as [::ffff:7f00:1]. Apply private-address checks to IP literals directly, not only through DNS lookup hooks. Use an IP parsing library or byte-level address checks instead of regex-only IPv6 matching.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| mcp-searxng | npm | < 1.2.1 | 1.2.1 |
- CriticalMLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebindingmlflowExploited
- Critical@zereight/mcp-gitlab Vulnerable to Server-Side Request Forgery@zereight/mcp-gitlab
- CriticalSSRF + LLM API key exfiltration via user-controlled basepath / baseUrl in 8 chat-model nodesflowise, flowise-components
- CriticalLocalAI POST /models/apply permits unauthenticated server-side request forgery through gallery URLsgithub.com/mudler/LocalAI
- CriticalFastMCP OpenAPI Provider has an SSRF & Path Traversal Vulnerabilityfastmcp
- CriticalBentoML SSRF Vulnerability in File Upload Processingbentoml
- HighSearXNG MCP Server: DNS-resolved Private Hostname SSRF in `web_url_read`mcp-searxng
- HighSearXNG MCP Server: Unbounded Response Body Read Bypasses URL Size Limit in `web_url_read`mcp-searxng
- MediumSearXNG Basic Authentication Credentials Exposed Through MCP Logs and JSON-RPC Error Responsesmcp-searxng
- MediumSearXNG MCP Server is Vulnerable to SSRF in web_url_read: the internal-address guard is disabled by default (MCP_HTTP_HARDEN off)mcp-searxng
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.