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, web_url_read passes a caller-supplied URL to the server-side fetch path while assertUrlAllowed() in src/url-reader.ts runs only when MCP_HTTP_HARDEN is enabled, even though MCP_HTTP_HARDEN is disabled by default in src/http-security.ts. In the default configuration, an attacker who influences the URL selected by a user or AI agent can make the server fetch loopback, private-network, or cloud metadata endpoint resources and return their contents into the model context. file:// URLs remain rejected, and the separate DNS-resolution and redirect-validation bypasses are outside this record. This issue is fixed in version 1.2.0.
CVE-2026-54688
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% 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.5
- EG Score
- 6.5(medium)
- EG Risk
- 45(Track)EG Risk 45/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 computedSeverity65% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 30%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
September 15, 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/48e5ecdcb4166a60b94c252dbe74b0a318110ac4[Security] SSRF in web_url_read · Issue #87 · ihor-sokoliuk/mcp-searxng · GitHub
https://github.com/ihor-sokoliuk/mcp-searxng/issues/87#issuecomment-4645453694SSRF in web_url_read: the internal-address guard is disabled by default (MCP_HTTP_HARDEN off) · Advisory · ihor-sokoliuk/mcp-searxng · GitHub
https://github.com/ihor-sokoliuk/mcp-searxng/security/advisories/GHSA-q87f-qc2r-2gw4Vendor Advisories for CVE-2026-54688(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(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× 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 21:52 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-19 21:47 UTCEG score recompute
- 2026-09-18 21:43 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 21:29 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 20:05 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-15 19:41 UTCEG score recompute
- 2026-09-15 19:14 UTCEG score recompute
- 2026-09-15 18:36 UTCEG score recompute
- 2026-08-19 19:42 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
Frequently asked(5)
What is CVE-2026-54688?
When was CVE-2026-54688 disclosed?
Is CVE-2026-54688 actively exploited?
What is the CVSS score of CVE-2026-54688?
How do I remediate CVE-2026-54688?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54688
Is Your Infrastructure Affected by CVE-2026-54688?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.