{"answers":{"affected":"2 open source packages ship an affected version, including 9router.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56676 exists.","fix":"Upgrade 9router to 0.5.2 or later.","what":"CVE-2026-56676 is a high-severity server-side request forgery vulnerability in decolua 9router, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-56676 and fix it if it is affected.\n\nWhat it is: CVE-2026-56676 is a high-severity server-side request forgery vulnerability in decolua 9router, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56676 exists.\n\nAffected packages and fixed versions:\n- 9router (npm): affected all versions; fixed in 0.5.2\n- 9router (npm): affected all versions; fixed in 0.5.2\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-56676/ (Markdown: https://insights.sbomify.com/CVE-2026-56676/index.md)","id":"CVE-2026-56676","markdown":"https://insights.sbomify.com/CVE-2026-56676/index.md","name":"CVE-2026-56676","record":{"aliases":["GHSA-cmhj-wh2f-9cgx"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"AI router proxy","requires_auth":"low_privilege","summary":"An authenticated attacker can exploit DNS rebinding in image prefetching to access internal services via the AI router proxy.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"description":"9Router is an AI router \u0026 token saver. Prior to 0.5.2, 9router validates image URLs by resolving the host before fetching, but open-sse/translator/concerns/image.js performs the later server-side image fetch with a separate DNS resolution. An authenticated attacker with access to the LLM proxy can use a vision-capable model and an attacker-controlled DNS name that first resolves to a public IP and then rebinds to an internal address, allowing server-side requests to internal-only HTTP services. This issue is fixed in version 0.5.2.","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":"9router: Image prefetch DNS rebinding allows SSRF to internal services","id":"CVE-2026-56676","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"9Router: Authenticated Server-Side Request Forgery (SSRF) via OIDC Provider Test Endpoint","id":"CVE-2026-56677"},"packages":[{"ecosystem":"npm","fixed":["0.5.2"],"introduced":["0"],"last_affected":[],"package":"9router","purl":null,"source":"GHSA-cmhj-wh2f-9cgx"},{"ecosystem":"npm","fixed":["0.5.2"],"introduced":["0"],"last_affected":[],"package":"9router","purl":"pkg:npm/9router","source":"GHSA-cmhj-wh2f-9cgx"}],"prev":{"headline":"9router: Reverse proxy locality collapse allows unauthenticated access to 9router /v1 APIs","id":"CVE-2026-56675"},"products":["9router"],"published":"2026-07-10","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-07-13","vendors":["decolua"]},"summary":"An authenticated attacker can exploit DNS rebinding in image prefetching to access internal services via the AI router proxy.","url":"https://insights.sbomify.com/CVE-2026-56676/"}