ASR AI Security Radar

AI security incident: SearXNG MCP Server: DNS-resolved Private Hostname SSRF in `web_url_read` (GHSA-mrvx-...

Source disclosure: June 19, 2026 | Published on Radar: October 26, 2026 | Source: GitHub Security Advisory | Classification confidence: 80%

Source disclosure is when the advisory appeared in this source (or was added to a catalog), not a confirmed date of exploitation. Radar publication is when this page became available.

This incident is part of the public archive. AI-specific signals are limited in the current source material, so source citations should be reviewed closely during triage. Review methodology.

SearXNG MCP Server: DNS-resolved Private Hostname SSRF in web url read DNS-resolved Private Hostname SSRF in web url read Summary The web url read MCP tool in mcp-searxng is vulnerable to Server-Side Request Forgery (SSRF) via DNS rebinding bypass. The assertUrlAllowed() function at src/url-reader.

Why This Is AI-Related

This advisory is part of the public incident archive, but the current source material uses limited explicit AI terminology, so the cited sources should be reviewed carefully when judging AI relevance and exposure.

  • Explicit AI-specific signals are limited in the current source material, so use the cited advisory to validate scope during triage.

Affected Workflow

Review connectors, retrieval plugins, webhook targets, file access paths, and outbound network policies around AI services.

Likely Attack Path

The flaw creates an unauthorized path to fetch, read, or exfiltrate sensitive data from connected systems or local files.

Impact

The flaw can expose internal data, local files, or connected systems through AI workflow connectors and supporting services. Severity HIGH. Classification confidence 80%. Source channel GHSA.

Detection And Triage Signals

  • Unexpected outbound requests from AI application components
  • Access to internal metadata endpoints, local files, or restricted datasets
  • Downloads or responses that contain internal documents, secrets, or embeddings

Recommended Response

  • Confirm whether the affected component can reach internal metadata, local files, or connected data stores.
  • Restrict outbound requests and sensitive data access paths until a patch or mitigation is in place.
  • Inspect logs for unusual downloads, webhook calls, retrieval requests, or responses containing internal content.

Compliance And Business Impact

Data exposure creates direct confidentiality risk and can trigger incident notification, contractual, and regulatory obligations.

Sources

Get weekly AI security updates

Get notified with incident context, likely impact, and response guidance.

Get Notified

More incidents