Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

Low severity, with a CVSS score of 3.1, published 19 August 2026.

Which products and versions are affected?

mcp-searxng (npm) SEMVER:introduced=0,fixed=1.12.0.

Is there a fix for This vulnerability?

Yes. mcp-searxng (npm): upgrade to 1.12.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is This vulnerability attacked?

It is attacked with local access or over the network, in a software library.

Check whether you run mcp-searxng (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

mcp-searxng credentials exposure in logging and error handling

Severity: low · CVSS 3.1 · Published 2026-08-19

mcp-searxng is a tool that integrates SearXNG search functionality with MCP (Model Context Protocol) clients. When configured with HTTP Basic Authentication credentials, the tool exposes these credentials—including username and password—through server startup logs, MCP notification messages, and JSON-RPC error responses. An attacker with access to server logs or an MCP client connection can recover credentials and use them to access the underlying SearXNG instance.

Technologies: mcp-searxng (npm). Vendors: npm.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: Low severity, with a CVSS score of 3.1, published 19 August 2026.
Which products and versions are affected?: mcp-searxng (npm) SEMVER:introduced=0,fixed=1.12.0.
Is there a fix for This vulnerability?: Yes. mcp-searxng (npm): upgrade to 1.12.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked with local access or over the network, in a software library.
Am I affected?: Check whether you run mcp-searxng (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

mcp-searxng (npm): upgrade to 1.12.0 or later
```
npm install mcp-searxng@1.12.0
```

Technical details

The vulnerability is a credential exposure flaw in mcp-searxng 1.11.0. The root cause is the failure to apply the existing redactSearxngInstanceUrl() redaction function before logging and error handling. The SEARXNG_URL environment variable contains credentials in the format http://username:password@host. These credentials are exposed in three paths: (1) startup console output via stderr, (2) MCP logging notifications sent to connected clients, and (3) JSON-RPC error responses when URL validation fails. The attack vector is local (via server logs) or requires an MCP client connection (network). No authentication bypass is needed—credentials are leaked passively. The issue is marked as patched in version 1.12.0.

Affected products

Ihor Sokoliuk mcp-searxng 1.11.0

Timeline

2026-07-26: disclosed
2026-08-19: advisory
2026-08-19: patched: Patched in version 1.12.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.