{"answers":{"affected":"2 open source packages ship an affected version, including hono. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-59139 in the wild and no public exploit code.","fix":"Upgrade hono to 4.9.7 or later.","what":"CVE-2025-59139 is a medium-severity denial of service vulnerability in honojs hono, published on 12 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-59139 and fix it if it is affected.\n\nWhat it is: CVE-2025-59139 is a medium-severity denial of service vulnerability in honojs hono, published on 12 Sep 2025. 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-2025-59139 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- hono (npm): affected all versions; fixed in 4.9.7\n- hono (npm): affected all versions; fixed in 4.9.7\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-2025-59139/ (Markdown: https://insights.sbomify.com/CVE-2025-59139/index.md)","id":"CVE-2025-59139","markdown":"https://insights.sbomify.com/CVE-2025-59139/index.md","name":"CVE-2025-59139","record":{"aliases":["GHSA-92vj-g62v-jqhh","MINI-qr2c-cccf-6gw7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript web framework","requires_auth":"none","summary":"Attackers can bypass body size limits in Hono framework by sending conflicting HTTP headers, potentially causing denial of service through resource exhaustion.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"hono","vendor":"hono"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Hono is a Web application framework that provides support for any JavaScript runtime. In versions prior to 4.9.7, a flaw in the `bodyLimit` middleware could allow bypassing the configured request body size limit when conflicting HTTP headers were present. The middleware previously prioritized the `Content-Length` header even when a `Transfer-Encoding: chunked` header was also included. According to the HTTP specification, `Content-Length` must be ignored in such cases. This discrepancy could allow oversized request bodies to bypass the configured limit. Most standards-compliant runtimes and reverse proxies may reject such malformed requests with `400 Bad Request`, so the practical impact depends on the runtime and deployment environment. If body size limits are used as a safeguard against large or malicious requests, this flaw could allow attackers to send oversized request bodies. The primary risk is denial of service (DoS) due to excessive memory or CPU consumption when handling very large requests. The implementation has been updated to align with the HTTP specification, ensuring that `Transfer-Encoding` takes precedence over `Content-Length`. The issue is fixed in Hono v4.9.7, and all users should upgrade immediately.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2026-05-19","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-05-19T10:25:45Z","kind":"github_poc","ref":"https://github.com/RoninForge/roninforge-hono","stars":0,"title":"Cursor plugin for Hono v4 (TypeScript edge web framework). 59 LLM regressions with BAD/CORRECT pairs. Pinned to hono ^4.12.19 (\u003e= 4.9.7 for CVE-2025-59139). Covers Express middleware leakage, v3-era removed APIs, RPC inference traps, Cloudflare Workers gotchas, security defaults, JSX SSR hardening."}],"tier":"poc_unverified"},"has_fix":true,"headline":"Hono has Body Limit Middleware Bypass","id":"CVE-2025-59139","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"backslash@0.2.1 contains malware after npm account takeover","id":"CVE-2025-59140"},"packages":[{"ecosystem":"npm","fixed":["4.9.7"],"introduced":["0"],"last_affected":[],"package":"hono","purl":null,"source":"GHSA-92vj-g62v-jqhh"},{"ecosystem":"npm","fixed":["4.9.7"],"introduced":["0"],"last_affected":[],"package":"hono","purl":"pkg:npm/hono","source":"GHSA-92vj-g62v-jqhh"}],"prev":{"headline":"WordPress Genemy theme \u003c= 1.6.6 - Server Side Request Forgery (SSRF) vulnerability","id":"CVE-2025-59138"},"products":["hono"],"published":"2025-09-12","related":[{"cvss_score":8.2,"headline":"Hono is Vulnerable to Authentication Bypass by IP Spoofing in AWS Lambda ALB conninfo","id":"CVE-2026-27700","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":8.2,"headline":"JWT Algorithm Confusion via Unsafe Default (HS256) in Hono JWT Middleware Allows Token Forgery and Auth Bypass","id":"CVE-2026-22817","kev_date_added":null,"published":"2026-01-13"},{"cvss_score":8.2,"headline":"JWT algorithm confusion in Hono JWK Auth Middleware when JWK lacks \"alg\" (untrusted header.alg fallback)","id":"CVE-2026-22818","kev_date_added":null,"published":"2026-01-13"},{"cvss_score":8.1,"headline":"Hono Improperly Authorizes JWT Audience Validation","id":"CVE-2025-62610","kev_date_added":null,"published":"2025-10-22"},{"cvss_score":7.5,"headline":"Hono: Arbitrary file access via serveStatic vulnerability","id":"CVE-2026-29045","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":7.5,"headline":"Hono contains a flaw in URL path parsing, potentially leading to path confusion","id":"CVE-2025-58362","kev_date_added":null,"published":"2025-09-04"},{"cvss_score":6.5,"headline":"hono/jsx does not isolate context per request, leading to cross-request data disclosure","id":"CVE-2026-59896","kev_date_added":null,"published":"2026-07-08"}],"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":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-12","vendors":["honojs"]},"summary":"Attackers can bypass body size limits in Hono framework by sending conflicting HTTP headers, potentially causing denial of service through resource exhaustion.","url":"https://insights.sbomify.com/CVE-2025-59139/"}