{"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-54688 exists.","fix":"Upgrade mcp-searxng to 1.2.1 or later.","what":"CVE-2026-54688 is a medium-severity server-side request forgery vulnerability in ihor-sokoliuk mcp-searxng, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-54688 and fix it if it is affected.\n\nWhat it is: CVE-2026-54688 is a medium-severity server-side request forgery vulnerability in ihor-sokoliuk mcp-searxng, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, 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-54688 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-54688/ (Markdown: https://insights.sbomify.com/CVE-2026-54688/index.md)","id":"CVE-2026-54688","markdown":"https://insights.sbomify.com/CVE-2026-54688/index.md","name":"CVE-2026-54688","record":{"aliases":["GHSA-q87f-qc2r-2gw4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MCP server library","requires_auth":"none","summary":"An attacker can force the server to fetch internal resources by supplying a malicious URL, exposing sensitive data to the AI model context.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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.2.0, web_url_read passes a caller-supplied URL to the server-side fetch path while assertUrlAllowed() in src/url-reader.ts runs only when MCP_HTTP_HARDEN is enabled, even though MCP_HTTP_HARDEN is disabled by default in src/http-security.ts. In the default configuration, an attacker who influences the URL selected by a user or AI agent can make the server fetch loopback, private-network, or cloud metadata endpoint resources and return their contents into the model context. file:// URLs remain rejected, and the separate DNS-resolution and redirect-validation bypasses are outside this record. 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: SSRF in web_url_read: the internal-address guard is disabled by default (MCP_HTTP_HARDEN off)","id":"CVE-2026-54688","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"mcp-searxng hardened-mode SSRF bypasses permit internal URL access","id":"CVE-2026-54689"},"packages":[{"ecosystem":"npm","fixed":["1.2.1"],"introduced":["0"],"last_affected":[],"package":"mcp-searxng","purl":null,"source":"GHSA-q87f-qc2r-2gw4"},{"ecosystem":"npm","fixed":["1.2.1"],"introduced":["0"],"last_affected":[],"package":"mcp-searxng","purl":"pkg:npm/mcp-searxng","source":"GHSA-q87f-qc2r-2gw4"}],"prev":{"headline":"n8n-nodes-sqlite3: Path traversal via user-controlled database file path (db_path parameter)","id":"CVE-2026-54687"},"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 force the server to fetch internal resources by supplying a malicious URL, exposing sensitive data to the AI model context.","url":"https://insights.sbomify.com/CVE-2026-54688/"}