Answer in brief
CVE-2026-54689 records a Medium severity (CVSS 6.3) vulnerability in mcp-searxng hardened-mode SSRF bypasses permit internal URL access. The current sources do not mark it as known exploited. The current feed maps ihor-sokoliuk/mcp-searxng (generic), mcp-searxng (npm), mcp-searxng (npm). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps ihor-sokoliuk/mcp-searxng (generic), mcp-searxng (npm), mcp-searxng (npm). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ihor-sokoliuk/mcp-searxnggeneric | < 1.2.0 | Not reported |
| mcp-searxngnpm | >=0 <1.2.1 | 1.2.1 |
| mcp-searxngnpm | <1.2.1 | 1.2.1 |
Published upstream
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 19, 2026
mcp-searxng is a Model Context Protocol server that gives AI assistants web search and URL-reading capabilities through SearXNG. Prior to 1.2.0, the web_url_read URL policy in src/url-reader.ts can be bypassed while MCP_HTTP_HARDEN is enabled and MCP_HTTP_ALLOW_PRIVATE_URLS is not enabled because redirect targets are not revalidated, 0.0.0.0 is not classified as an internal address, and IPv4-mapped IPv6 literals canonicalized to hexadecimal form are not recognized. These inputs allow an attacker-influenced tool call to make the MCP server fetch loopback or internal HTTP resources and return content from local services, private APIs, service-mesh endpoints, or cloud metadata endpoints. The separate hostname-to-private-address case addressed by the earlier partial fix is not part of these residual bypasses. This issue is fixed in version 1.2.0.
Quoted source text, attributed separately from HOL analysis.