{"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-54689 exists.","fix":"Upgrade mcp-searxng to 1.2.1 or later.","what":"CVE-2026-54689 is a medium-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, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-54689 and fix it if it is affected.\n\nWhat it is: CVE-2026-54689 is a medium-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, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54689 exists.\n\nAffected packages and fixed versions:\n- mcp-searxng (npm): affected all versions; fixed in 1.2.1\n- mcp-searxng (npm): affected all versions; fixed in 1.2.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-54689/ (Markdown: https://insights.sbomify.com/CVE-2026-54689/index.md)","id":"CVE-2026-54689","markdown":"https://insights.sbomify.com/CVE-2026-54689/index.md","name":"CVE-2026-54689","record":{"aliases":["GHSA-wppf-h75h-6pm6"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"MCP SearXNG server","requires_auth":"none","summary":"An attacker can bypass SSRF protections in mcp-searxng to access internal network resources and cloud metadata endpoints.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"mcp-searxng is a Model Context Protocol server that gives AI assistants web search and URL-reading capabilities through SearXNG. Prior to 1.2.0, the web_url_read URL policy in src/url-reader.ts can be bypassed while MCP_HTTP_HARDEN is enabled and MCP_HTTP_ALLOW_PRIVATE_URLS is not enabled because redirect targets are not revalidated, 0.0.0.0 is not classified as an internal address, and IPv4-mapped IPv6 literals canonicalized to hexadecimal form are not recognized. These inputs allow an attacker-influenced tool call to make the MCP server fetch loopback or internal HTTP resources and return content from local services, private APIs, service-mesh endpoints, or cloud metadata endpoints. The separate hostname-to-private-address case addressed by the earlier partial fix is not part of these residual bypasses. This issue is fixed in version 1.2.0.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"mcp-searxng hardened-mode SSRF bypasses permit internal URL access","id":"CVE-2026-54689","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"datamodel-code-generator vulnerable to SSRF via JSON-Schema `$ref` to HTTP URL (silent by default)","id":"CVE-2026-54690"},"packages":[{"ecosystem":"npm","fixed":["1.2.1"],"introduced":["0"],"last_affected":[],"package":"mcp-searxng","purl":null,"source":"GHSA-wppf-h75h-6pm6"},{"ecosystem":"npm","fixed":["1.2.1"],"introduced":["0"],"last_affected":[],"package":"mcp-searxng","purl":"pkg:npm/mcp-searxng","source":"GHSA-wppf-h75h-6pm6"}],"prev":{"headline":"mcp-searxng: SSRF in web_url_read: the internal-address guard is disabled by default (MCP_HTTP_HARDEN off)","id":"CVE-2026-54688"},"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-17","vendors":["ihor-sokoliuk"]},"summary":"An attacker can bypass SSRF protections in mcp-searxng to access internal network resources and cloud metadata endpoints.","url":"https://insights.sbomify.com/CVE-2026-54689/"}