CVE-2026-58483: mcp-searxng: Unbounded Response Body Read Bypasses URL Size Limit in `web_url_read`

Published Sep 15, 2026
·
Updated

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, weburlread in src/index.ts passes a caller-supplied URL to readUrlContent() in src/url-reader.ts, where checkContentLength() treats a missing Content-Length header as an inconclusive preflight and the normal and error paths then consume the complete body with response.text(). A server that omits Content-Length can therefore bypass URLREADMAXCONTENTLENGTHBYTES and force unbounded memory use. The resulting string is also processed by NodeHtmlMarkdown.translate(), increasing CPU consumption and allowing an unauthenticated HTTP client to cause denial of service. This issue is fixed in version 1.7.1.

Affected Software

1 affected component
mcp-searxng<1.7.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade mcp-searxng to a version that resolves this vulnerability.

    Fixed in 1.7.1

Event History

Sep 15, 2026
CVE Published
via MITRE·05:48 PM
Data Sourced
via MITRE·05:48 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this denial-of-service issue?

mcp-searxng versions prior to 1.7.1 are affected where an unauthenticated HTTP client can invoke the web_url_read capability. The issue can be triggered by directing the server to a response that omits the Content-Length header.

2

What does an attacker need to do to exploit this?

An attacker needs network access to the HTTP interface and does not need authentication or user interaction. They supply a URL whose server returns a body without Content-Length, causing mcp-searxng to read the complete response and process it as HTML-to-Markdown content.

3

Is the configured URL response-size limit sufficient protection?

No. Before 1.7.1, URL_READ_MAX_CONTENT_LENGTH_BYTES can be bypassed when the upstream response omits Content-Length, because the implementation treats the absent header as inconclusive and reads the full body.

4

What is the remediation?

Upgrade mcp-searxng to version 1.7.1. This version fixes the unbounded response-body read in web_url_read.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203