# CVE-2026-54689: mcp-searxng hardened-mode SSRF bypasses permit internal URL access

> An attacker can bypass SSRF protections in mcp-searxng to access internal network resources and cloud metadata endpoints.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-wppf-h75h-6pm6

## What is CVE-2026-54689?

CVE-2026-54689 is a medium-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, and only if a user opens a file or follows a link.

### 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.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.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

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


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

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

Upgrade mcp-searxng to 1.2.1 or later.

## Is CVE-2026-54689 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54689 is a medium-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, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54689 exists.

Affected packages and fixed versions:
- mcp-searxng (npm): affected all versions; fixed in 1.2.1
- mcp-searxng (npm): affected all versions; fixed in 1.2.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-54689/ (Markdown: https://insights.sbomify.com/CVE-2026-54689/index.md)
```

## Sources

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

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