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.
CVE-2026-54689
This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(medium)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity63% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
September 17, 2026
Advisory Details (4)
Auto-updated Sep 15, 2026v1.2.0
Patch available: ihor-sokoliuk/mcp-searxng v1.2.0
https://github.com/ihor-sokoliuk/mcp-searxng/releases/tag/v1.2.0commit 48e5ecdcb416 (ihor-sokoliuk/mcp-searxng)
Patch available: ihor-sokoliuk/mcp-searxng v1.2.0 (contains commit 48e5ecdcb416)
https://github.com/ihor-sokoliuk/mcp-searxng/commit/48e5ecdcb4166a60b94c252dbe74b0a318110ac4fix(url-reader): block DNS-rebinding SSRF via socket-level lookup guard (CWE-918)
Upstream fix in progress (PR #79 · ihor-sokoliuk/mcp-searxng, state=closed)
https://github.com/ihor-sokoliuk/mcp-searxng/pull/79Additional hardened-mode SSRF bypasses not covered by PR #79 · Advisory · ihor-sokoliuk/mcp-searxng · GitHub
https://github.com/ihor-sokoliuk/mcp-searxng/security/advisories/GHSA-wppf-h75h-6pm6Vendor Advisories for CVE-2026-54689(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| mcp-searxng | — | 1.2.1 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-19 19:32 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 18:53 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-17 18:13 UTCEG score recompute
- 2026-09-16 20:05 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-15 18:36 UTCEG score recompute
- 2026-08-19 19:42 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-200 · CWE-918
Frequently asked(5)
What is CVE-2026-54689?
When was CVE-2026-54689 disclosed?
Is CVE-2026-54689 actively exploited?
What is the CVSS score of CVE-2026-54689?
How do I remediate CVE-2026-54689?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54689
Is Your Infrastructure Affected by CVE-2026-54689?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.