Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.1amended

SearXNG MCP Server: DNS-resolved Private Hostname SSRF in web_url_read

CVE-2026-58485GHSA-mrvx-jmjw-vggc

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (mcp-searxng 1.7.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.1 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
EPSS
  • CVE-2026-58485: 0.19% estimated exploitation activity in the next 30 days; percentile 8.50 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

DNS-resolved Private Hostname SSRF in weburlread Summary The weburlread MCP tool in mcp-searxng is vulnerable to Server-Side Request Forgery (SSRF) via DNS rebinding bypass. The assertUrlAllowed() function at src/url-reader.ts:85-93 validates only the syntactic hostname string against a private IP/hostname blocklist without performing DNS resolution. An attacker who controls a domain that resolves to a private or loopback IP address (e.g., via a wildcard DNS service like nip.io, or a custom DNS entry) can bypass the security check and cause the MCP server to read arbitrary internal HTTP services reachable from the server host. This allows exfiltration of sensitive data from internal services with no authentication required in the default HTTP configuration. Details The vulnerable code is in src/url-reader.ts, where the assertUrlAllowed() function performs a hostname-only string comparison: This function checks whether url.hostname lexically matches a private address pattern but never…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-mrvx-jmjw-vggc

  2. Revision 1 · created ·

    Published from osv record GHSA-mrvx-jmjw-vggc

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-58485

Advisory: SearXNG MCP Server: DNS-resolved Private Hostname SSRF in `web_url_read`
IDs: CVE-2026-58485, GHSA-mrvx-jmjw-vggc
Record: https://patchnext.com/advisories/cve-2026-58485 (revision 2, source checked 26 Oct 2026, 12:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mcp-searxng 1.7.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm mcp-searxng: affected < 1.7.1; fixed in 1.7.1

## Suggested inspection (read-only)
- `npm ls mcp-searxng --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mcp-searxng.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-mrvx-jmjw-vggc (OSV record GHSA-mrvx-jmjw-vggc lists affected ranges: npm mcp-searxng >=0 <1.7.1 (fixed))
- Verified: https://github.com/advisories/GHSA-mrvx-jmjw-vggc (GitHub-reviewed advisory GHSA-mrvx-jmjw-vggc lists affected ranges: npm mcp-searxng >=0 <1.7.1)

Commands are suggestions: review each one before running it.

Loading voting…