{"answers":{"affected":"2 open source packages ship an affected version, including hono.","exploited":"There is no known exploitation of CVE-2026-71849 in the wild and no public exploit code.","fix":"Upgrade hono to 4.12.34 or later.","what":"CVE-2026-71849 is a low-severity vulnerability in honojs hono, published on 7 Aug 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-71849 and fix it if it is affected.\n\nWhat it is: CVE-2026-71849 is a low-severity vulnerability in honojs hono, published on 7 Aug 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-71849 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- hono (npm): affected from 4.7.0; fixed in 4.12.34\n- hono (npm): affected from 4.7.0; fixed in 4.12.34\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-71849/ (Markdown: https://insights.sbomify.com/CVE-2026-71849/index.md)","id":"CVE-2026-71849","markdown":"https://insights.sbomify.com/CVE-2026-71849/index.md","name":"CVE-2026-71849","record":{"aliases":["CLEANSTART-2026-AV60851","ECHO-48a8-f364-cd95","GHSA-79qm-7rj5-m7r9","MINI-5x82-w7h7-45p8","MINI-6447-r75f-32fx","MINI-6mhc-j8j4-79q2","MINI-9cpg-qf2r-wcxr","MINI-f24c-hcc5-qwrf","MINI-gq3m-hr4f-9g8r","MINI-jwvj-gh43-cv73","MINI-ph9h-r76v-rx57","MINI-vrpm-gjhc-g2fv","MINI-whj5-58j2-qw49","MINI-xw5p-w23m-5hhm"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript web framework","requires_auth":"none","summary":"The Hono framework's proxy helper fails to remove hop-by-hop headers, potentially disclosing internal metadata to clients.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Hono is a Web application framework that provides support for any JavaScript runtime. From 4.7.0 to 4.12.33, the Proxy Helper proxy() function in hono/proxy does not remove response headers named by the origin's Connection header. Per RFC 9110 Section 7.6.1, an intermediary must remove the header fields listed in a message's Connection header field before forwarding the message, in addition to the well known hop by hop headers, but the proxy() function only removed the well known hop by hop headers, including Connection itself, from origin responses. A client may therefore receive response headers that the origin intended only for its immediate peer, disclosing connection scoped or internal metadata contained in such headers, when an application proxies responses from an origin that declares additional, non standard headers as hop by hop via the Connection response header. This issue is fixed in version 4.12.34.","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: Proxy Helper does not remove response headers listed in the `Connection` header","id":"CVE-2026-71849","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Hono: `memo()` retains SSR output across requests, leading to cross-user data disclosure","id":"CVE-2026-71850"},"packages":[{"ecosystem":"npm","fixed":["4.12.34"],"introduced":["4.7.0"],"last_affected":[],"package":"hono","purl":null,"source":"GHSA-79qm-7rj5-m7r9"},{"ecosystem":"npm","fixed":["4.12.34"],"introduced":["4.7.0"],"last_affected":[],"package":"hono","purl":"pkg:npm/hono","source":"GHSA-79qm-7rj5-m7r9"}],"prev":{"headline":"Hono: Algorithmic Complexity DoS in Language Middleware","id":"CVE-2026-71848"},"products":["hono"],"published":"2026-08-07","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-10","vendors":["honojs"]},"summary":"The Hono framework's proxy helper fails to remove hop-by-hop headers, potentially disclosing internal metadata to clients.","url":"https://insights.sbomify.com/CVE-2026-71849/"}