# CVE-2026-58485: mcp-searxng: DNS-resolved Private Hostname SSRF in `web_url_read`

> An attacker can exploit a DNS rebinding flaw in mcp-searxng to access internal network resources and sensitive data via the web_url_read function.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-mrvx-jmjw-vggc

## What is CVE-2026-58485?

CVE-2026-58485 is a high-severity server-side request forgery vulnerability in ihor-sokoliuk mcp-searxng, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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 receives its caller-controlled URL through src/index.ts and validates only the literal hostname in assertUrlAllowed() within src/url-reader.ts before undiciFetch() performs operating-system DNS resolution. A public-looking attacker-controlled hostname that resolves to a private, loopback, link-local, or cloud-metadata address therefore passes the lexical check and causes the MCP server to connect to the internal destination. In the default HTTP configuration, an unauthenticated network client can use this path to read internal services, expose credentials or service tokens, and enumerate reachable internal hosts; in STDIO deployments, prompt-influenced tool selection can provide the malicious URL. Direct private IP literals are blocked, and MCP_HTTP_ALLOW_PRIVATE_URLS remains an explicit opt-out. This issue is fixed in version 1.7.1.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-58485?

2 open source packages ship an affected version, including mcp-searxng.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mcp-searxng` | npm | All versions | 1.7.1 |
| `mcp-searxng` | npm | All versions | 1.7.1 |

## How do I fix CVE-2026-58485?

Upgrade mcp-searxng to 1.7.1 or later.

## Is CVE-2026-58485 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58485 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-58485 and fix it if it is affected.

What it is: CVE-2026-58485 is a high-severity server-side request forgery vulnerability in ihor-sokoliuk mcp-searxng, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58485 exists.

Affected packages and fixed versions:
- mcp-searxng (npm): affected all versions; fixed in 1.7.1
- mcp-searxng (npm): affected all versions; fixed in 1.7.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-58485/ (Markdown: https://insights.sbomify.com/CVE-2026-58485/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-58485
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-58485
- OSV: https://osv.dev/vulnerability/CVE-2026-58485

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-58485/
Summaries are generated and may contain mistakes; the official description above is the record.