{"answers":{"affected":"2 open source packages ship an affected version, including mcp-searxng.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58485 exists.","fix":"Upgrade mcp-searxng to 1.7.1 or later.","what":"CVE-2026-58485 is a high-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, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-58485 and fix it if it is affected.\n\nWhat it is: CVE-2026-58485 is a high-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, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58485 exists.\n\nAffected packages and fixed versions:\n- mcp-searxng (npm): affected all versions; fixed in 1.7.1\n- mcp-searxng (npm): affected all versions; fixed in 1.7.1\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-58485/ (Markdown: https://insights.sbomify.com/CVE-2026-58485/index.md)","id":"CVE-2026-58485","markdown":"https://insights.sbomify.com/CVE-2026-58485/index.md","name":"CVE-2026-58485","record":{"aliases":["GHSA-mrvx-jmjw-vggc"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MCP server","requires_auth":"none","summary":"An attacker can exploit a DNS rebinding flaw in mcp-searxng to access internal network resources and sensitive data via the web_url_read function.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"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, web_url_read receives its caller-controlled URL through src/index.ts and validates only the literal hostname in assertUrlAllowed() within src/url-reader.ts before undiciFetch() performs operating-system DNS resolution. A public-looking attacker-controlled hostname that resolves to a private, loopback, link-local, or cloud-metadata address therefore passes the lexical check and causes the MCP server to connect to the internal destination. In the default HTTP configuration, an unauthenticated network client can use this path to read internal services, expose credentials or service tokens, and enumerate reachable internal hosts; in STDIO deployments, prompt-influenced tool selection can provide the malicious URL. Direct private IP literals are blocked, and MCP_HTTP_ALLOW_PRIVATE_URLS remains an explicit opt-out. This issue is fixed in version 1.7.1.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"mcp-searxng: DNS-resolved Private Hostname SSRF in `web_url_read`","id":"CVE-2026-58485","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"HedgeDoc: Denial-of-service via YAML alias expansion in note frontmatter","id":"CVE-2026-58486"},"packages":[{"ecosystem":"npm","fixed":["1.7.1"],"introduced":["0"],"last_affected":[],"package":"mcp-searxng","purl":null,"source":"GHSA-mrvx-jmjw-vggc"},{"ecosystem":"npm","fixed":["1.7.1"],"introduced":["0"],"last_affected":[],"package":"mcp-searxng","purl":"pkg:npm/mcp-searxng","source":"GHSA-mrvx-jmjw-vggc"}],"prev":{"headline":"Network-AI: Poisoned environment backup manifest allows arbitrary recursive deletion during backup pruning","id":"CVE-2026-58484"},"products":["mcp-searxng"],"published":"2026-09-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-15","vendors":["ihor-sokoliuk"]},"summary":"An attacker can exploit a DNS rebinding flaw in mcp-searxng to access internal network resources and sensitive data via the web_url_read function.","url":"https://insights.sbomify.com/CVE-2026-58485/"}