UTC
Medium

SearXNG Basic Authentication Credentials Exposed Through MCP Logs and JSON-RPC Error Responses

GHSA-hjwh-xvfw-qrwj · published 2026-08-19

Severity
Medium
CVSS score
5.5
Chance of exploitation (EPSS)
No CVE
Fixed in
1.12.0
What it is

This is a sensitive credential disclosure vulnerability. The following parties may obtain the credentials: 1. A connected MCP client receiving logging notifications. 2. A client capable of invoking a tool and receiving JSON-RPC errors. 3. A user or process with access to captured stderr output. 4. A centralized logging or monitoring system collecting application logs. 5. Other users with access to shared log files or container logs. The exposed credentials may allow an attacker to authenticate directly to the configured SearXNG instance. Depending on the SearXNG deployment and the permissions associated with the account, this may allow: 1. Unauthorized use of a private SearXNG service. 2.

What to do

Upgrade mcp-searxng to 1.12.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

If you cannot upgrade yet

Apply redactSearxngInstanceUrl() before including any SearXNG URL in console or MCP logging: Do not include raw configuration values in validation errors. A generic error can be returned instead: For malformed URLs: The following additional changes are recommended: 1. Redact URLs before writing them to stderr. 2. Redact secrets before sending MCP logging notifications. 3. Avoid including raw environment-variable values in exceptions. 4. Avoid returning detailed stack traces containing secrets to MCP clients. 5. Mark SEARXNG_URL as secret in .mcp/server.json: 6.

Affected
PackageRegistryAffectedFixed in
mcp-searxngnpm< 1.12.01.12.0

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].