{"answers":{"affected":"2 open source packages ship an affected version, including @hono/node-server.","exploited":"There is no known exploitation of CVE-2026-126210 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"Upgrade @hono/node-server to a fixed version for your release line: 1.19.18 or 2.1.6.","what":"CVE-2026-126210 is a medium-severity security feature bypass vulnerability in honojs node-server, published on 12 Nov 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-126210 and fix it if it is affected.\n\nWhat it is: CVE-2026-126210 is a medium-severity security feature bypass vulnerability in honojs node-server, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-126210 in the wild and no public exploit code.\nExposure: An affected version is exposed as installed. No special setting or call is needed.\n\nAffected packages and fixed versions:\n- @hono/node-server (npm): affected all versions; fixed in 1.19.18\n- @hono/node-server (npm): affected from 2.0.0; fixed in 2.1.6\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-126210/ (Markdown: https://insights.sbomify.com/CVE-2026-126210/index.md)","id":"CVE-2026-126210","markdown":"https://insights.sbomify.com/CVE-2026-126210/index.md","name":"CVE-2026-126210","record":{"aliases":["GHSA-jpvv-r467-5p4w"],"analysis":{"component_type":"library","exploitable_when_present":false,"fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js web server","requires_auth":"none","requires_specific_call":false,"summary":"Unauthenticated clients can use backslashes in request paths to reach routes blocked by upstream reverse proxies or WAFs; Hono Node.js app operators should care.","user_interaction":"not_required","vuln_class":"security_feature_bypass","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","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-436","name":"Interpretation Conflict"}],"description":"@hono/node-server allows running the Hono application on Node.js. Prior to 1.19.18 and from 2.0.0 until 2.1.6, the server passes a raw request-target containing a backslash in its path to the WHATWG URL parser, which treats the backslash as a path separator and resolves dot segments. A reverse proxy, load balancer, or web application firewall that preserves the backslash and applies path-based rules to the original request can therefore permit a request that the application normalizes to a blocked route. This lets an unauthenticated client reach route content that the upstream component was intended to deny, while Hono application access controls are unaffected because they operate on the normalized path. This issue is fixed in versions 1.19.18 and 2.1.6.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"@hono/node-server: Backslash in the request path is parsed as a path separator, bypassing path-based access control at a reverse proxy","id":"CVE-2026-126210","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":5,"next":{"headline":"Privilege escalation in FortiAnalyzer","id":"CVE-2026-126211"},"nickname":null,"packages":[{"ecosystem":"npm","fixed":["1.19.18"],"introduced":["0"],"last_affected":[],"package":"@hono/node-server","purl":null,"source":"GHSA-jpvv-r467-5p4w"},{"ecosystem":"npm","fixed":["2.1.6"],"introduced":["2.0.0"],"last_affected":[],"package":"@hono/node-server","purl":null,"source":"GHSA-jpvv-r467-5p4w"}],"prev":{"headline":"Loofah allowed_uri? treats javascript: alert(1) as safe","id":"CVE-2026-126209"},"products":["node-server"],"published":"2026-11-12","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-11-12","vendors":["honojs"]},"summary":"Unauthenticated clients can use backslashes in request paths to reach routes blocked by upstream reverse proxies or WAFs; Hono Node.js app operators should care.","url":"https://insights.sbomify.com/CVE-2026-126210/"}