CVE-2026-54689

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (7th percentile of EPSS-scored CVEs). 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.3Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
44
EG Risk 44/100CISA SSVC

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 computed
Severity63% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 19, 2026

Last Modified

September 30, 2026

Advisory Details (4)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v1.2.0

Patch available: ihor-sokoliuk/mcp-searxng v1.2.0

https://github.com/ihor-sokoliuk/mcp-searxng/releases/tag/v1.2.0
github_commit Patch Available

commit 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
github_pr

fix(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/79
github Patch Available🟡 PoC Available

Additional 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-6pm6

Vendor 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)
PackageVulnerable rangeFix by version rangeDependents
mcp-searxng—
  • every version up to 1.2.1: fixed in 1.2.1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 33× 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.

  1. 2026-10-05 05:10 UTCEG score recompute
  2. 2026-10-04 23:22 UTCEPSS rescore
  3. 2026-10-04 02:41 UTCEG score recompute
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-03 00:42 UTCEG score recompute
  6. 2026-10-02 17:56 UTCEPSS rescore
  7. 2026-10-01 22:46 UTCEG score recompute
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 18:11 UTCEG score recompute
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-30 08:41 UTCEG score recompute
  12. 2026-09-29 15:22 UTCEPSS rescore
  13. 2026-09-29 07:31 UTCEG score recompute
  14. 2026-09-28 13:51 UTCEPSS rescore
  15. 2026-09-28 06:51 UTCEG score recompute
  16. 2026-09-27 13:48 UTCEPSS rescore
  17. 2026-09-27 06:12 UTCEG score recompute
  18. 2026-09-26 15:59 UTCEPSS rescore
  19. 2026-09-25 00:49 UTCEG score recompute
  20. 2026-09-24 14:04 UTCEPSS rescore
  21. 2026-09-23 22:15 UTCEG score recompute
  22. 2026-09-23 17:54 UTCEPSS rescore
  23. 2026-09-22 21:35 UTCEG score recompute
  24. 2026-09-21 20:57 UTCEG score recompute
  25. 2026-09-20 20:16 UTCEPSS rescore
Show 9 more
  1. 2026-09-19 19:32 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 18:53 UTCEG score recompute
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-17 18:13 UTCEG score recompute
  6. 2026-09-16 20:05 UTCEG score recompute
  7. 2026-09-16 14:08 UTCEPSS rescore
  8. 2026-09-15 18:36 UTCEG score recompute
  9. 2026-08-19 19:42 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-54689?
CVE-2026-54689 is a medium vulnerability published on August 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 weburlread URL policy in src/url-reader.ts can be bypassed while MCPHTTPHARDEN is enabled and MCPHTTPALLOWPRIVATEURLS is not enabled because redirect…
When was CVE-2026-54689 disclosed?
CVE-2026-54689 was first published on August 19, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54689 actively exploited?
CVE-2026-54689 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54689?
CVE-2026-54689 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54689?
A fix for CVE-2026-54689 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54689 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54689

Explore →

Is Your Infrastructure Affected by CVE-2026-54689?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs