CVE-2026-54689: ihor-sokoliuk mcp-searxng · Information Exposure
Affects ihor-sokoliuk mcp-searxngSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 1.2.0 when convenient.
Data as of 30 Oct 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.2.0
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade mcp-searxng and ihor-sokoliuk/mcp-searxng to 1.2.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ihor-sokoliukmcp-searxng | Affected
| Fixed in
|
GitHubihor-sokoliuk/mcp-searxngpkg:github/ihor-sokoliuk/mcp-searxngOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade mcp-searxng to version 1.2.0 or later, where this vulnerability is fixed. No other mitigation is required as the fix addresses the root cause by properly validating redirect targets and classifying internal addresses.
Description
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.
References
- github.com/ihor-sokoliuk/mcp-searxng/security/advisories/GHSA-wppf-h75h-6pm6 (opens in a new tab)
- github.com/ihor-sokoliuk/mcp-searxng/pull/79 (opens in a new tab)
- github.com/ihor-sokoliuk/mcp-searxng/commit/48e5ecdcb4166a60b94c252dbe74b0a318110ac4 (opens in a new tab)
- github.com/ihor-sokoliuk/mcp-searxng/releases/tag/v1.2.0 (opens in a new tab)