Skip to main content
VulnerabilityPublished

CVE-2026-58483: ihor-sokoliuk mcp-searxng · Uncontrolled Resource Consumption

Affects ihor-sokoliuk mcp-searxngSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 1.7.1 soon.

Data as of 30 Oct 2026, 20:25 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.7.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.7.1.

Affected software

ProductAffectedFixed in
ihor-sokoliukmcp-searxngAffected
  • <1.7.1
Fixed in
  • 1.7.1
GitHubihor-sokoliuk/mcp-searxngpkg:github/ihor-sokoliuk/mcp-searxngOther threatsAffected
  • <1.7.1
Fixed in
  • 1.7.1

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.7.1 or later, where this vulnerability is fixed. No other mitigations are indicated by the vendor advisory.

Description

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.

References

Community reviews

Loading reviews…