mcp-searxng is a Model Context Protocol server that gives AI assistants web search and URL-reading capabilities through SearXNG. Prior to 1.7.1, web_url_read in src/index.ts passes a caller-supplied URL to readUrlContent() in src/url-reader.ts, where checkContentLength() treats a missing Content-Length header as an inconclusive preflight and the normal and error paths then consume the complete body with response.text(). A server that omits Content-Length can therefore bypass URL_READ_MAX_CONTENT_LENGTH_BYTES and force unbounded memory use. The resulting string is also processed by NodeHtmlMarkdown.translate(), increasing CPU consumption and allowing an unauthenticated HTTP client to cause denial of service. This issue is fixed in version 1.7.1.
CVE-2026-58483
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (51st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-79124 (ENISA EUVD)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHmedium confidence
- EG Risk
- 65EG Risk 65/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.7%
- EPSS %ILE
- 51st
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
September 15, 2026
Last Modified
September 30, 2026
Advisory Details (4)
Auto-updated Sep 15, 2026v1.7.1
Patch available: ihor-sokoliuk/mcp-searxng v1.7.1
https://github.com/ihor-sokoliuk/mcp-searxng/releases/tag/v1.7.1commit f5a947ed1650 (ihor-sokoliuk/mcp-searxng)
Patch available: ihor-sokoliuk/mcp-searxng v1.7.1 (contains commit f5a947ed1650)
https://github.com/ihor-sokoliuk/mcp-searxng/commit/f5a947ed1650daed10fbdcd53c0db5a86489ffe4security(url-reader): enforce size limit via streaming body cap (SEC-022)
Patch available: ihor-sokoliuk/mcp-searxng v1.7.1 (PR #121 merged 2026-06-18)
https://github.com/ihor-sokoliuk/mcp-searxng/pull/121Unbounded Response Body Read Bypasses URL Size Limit in `web_url_read` · Advisory · ihor-sokoliuk/mcp-searxng · GitHub
https://github.com/ihor-sokoliuk/mcp-searxng/security/advisories/GHSA-xcqx-9jf5-w339Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| mcp-searxng | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 47× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-30 17:20 UTCEG score recompute
- 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-25 14:16 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-23 15:20 UTCEG score recompute
- 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-18 03:27 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-16 13:02 UTCEG score recompute
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
Show 57 moreShow fewer
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-12 15:53 UTCEG score recompute
- 2026-10-11 19:29 UTCEG score recompute
- 2026-10-11 16:52 UTCEG score recompute
- 2026-10-11 14:14 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-11 06:27 UTCEG score recompute
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-10 04:50 UTCEG score recompute
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-08 22:15 UTCEG score recompute
- 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-08 07:37 UTCEG score recompute
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-07 03:50 UTCEG score recompute
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-06 02:18 UTCEG score recompute
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-05 00:28 UTCEG score recompute
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-03 22:49 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-02 21:11 UTCEG score recompute
- 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-10-02 08:25 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-30 18:09 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-29 20:19 UTCEG score recompute
- 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
- 2026-09-29 04:37 UTCEG score recompute
- 2026-09-28 15:51 UTCEG score recompute
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-09-27 14:20 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-09-27 01:33 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-09-26 12:47 UTCEG score recompute
- 2026-09-24 21:45 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.7% · 49th percentile
- 2026-09-23 20:14 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-22 18:43 UTCEG score recompute
- 2026-09-22 05:56 UTCEG score recompute
- 2026-09-21 04:26 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-20 02:52 UTCEG score recompute
- 2026-09-19 01:20 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-17 23:49 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-16 21:34 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-09-15 19:37 UTCEG score recompute
- 2026-09-15 18:32 UTCEG score recompute
- 2026-09-15 17:58 UTCEG score recomputeFirst assessed: 7.5 HIGH
- 2026-09-15 17:57 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
3 shownnpm:mcp-searxng
Frequently asked(5)
What is CVE-2026-58483?
When was the CVE record for CVE-2026-58483 published?
Is CVE-2026-58483 actively exploited?
What is the CVSS score of CVE-2026-58483?
How do I remediate CVE-2026-58483?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-58483
Is Your Infrastructure Affected by CVE-2026-58483?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.