{"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-56682 exists.","fix":"Upgrade 9router to 0.5.8 or later.","what":"CVE-2026-56682 is a medium-severity vulnerability in decolua 9router, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-56682 and fix it if it is affected.\n\nWhat it is: CVE-2026-56682 is a medium-severity vulnerability in decolua 9router, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56682 exists.\n\nAffected packages and fixed versions:\n- 9router (npm): affected all versions; fixed in 0.5.8\n- 9router (npm): affected all versions; fixed in 0.5.8\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-56682/ (Markdown: https://insights.sbomify.com/CVE-2026-56682/index.md)","id":"CVE-2026-56682","markdown":"https://insights.sbomify.com/CVE-2026-56682/index.md","name":"CVE-2026-56682","record":{"aliases":["GHSA-32gc-64m7-hj7v"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"AI router application","requires_auth":"none","summary":"Attackers can bypass login lockout mechanisms by spoofing IP headers, enabling unthrottled password guessing and potential administrative account takeover.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-807","name":"Reliance on Untrusted Inputs in a Security Decision"},{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"9Router is an AI router \u0026 token saver. Prior to 0.5.6, 9Router deployments that allow requests to reach Next.js without the sanitizing custom-server.js wrapper use the client-supplied X-9r-Real-Ip value as the bucket key in getClientIp, checkLock, and recordFail in src/lib/auth/loginLimiter.js for POST /api/auth/login. A remote unauthenticated attacker can rotate the header on every password guess so each request uses a new failed-attempt bucket and the five-attempt progressive lockout never returns HTTP 429. This permits unthrottled password guessing against the dashboard login and can lead to an administrative session if the password is recovered. This issue is fixed in version 0.5.6.","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: Login Brute-Force Lockout Bypass via Spoofable X-9r-Real-Ip Header","id":"CVE-2026-56682","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Valkey: TLS pending-data processing use-after-free may allow remote code execution","id":"CVE-2026-56684"},"packages":[{"ecosystem":"npm","fixed":["0.5.8"],"introduced":["0"],"last_affected":[],"package":"9router","purl":null,"source":"GHSA-32gc-64m7-hj7v"},{"ecosystem":"npm","fixed":["0.5.8"],"introduced":["0"],"last_affected":[],"package":"9router","purl":"pkg:npm/9router","source":"GHSA-32gc-64m7-hj7v"}],"prev":{"headline":"9Router: Authentication Bypass in Public LLM API via Spoofable X-9r-Real-Ip Header","id":"CVE-2026-56681"},"products":["9router"],"published":"2026-09-22","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-22","vendors":["decolua"]},"summary":"Attackers can bypass login lockout mechanisms by spoofing IP headers, enabling unthrottled password guessing and potential administrative account takeover.","url":"https://insights.sbomify.com/CVE-2026-56682/"}