{"answers":{"affected":"2 open source packages ship an affected version, including hono. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48913 exists.","fix":"Upgrade hono to 4.6.5 or later.","what":"CVE-2024-48913 is a medium-severity vulnerability in honojs hono, published on 15 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-48913 and fix it if it is affected.\n\nWhat it is: CVE-2024-48913 is a medium-severity vulnerability in honojs hono, published on 15 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48913 exists.\n\nAffected packages and fixed versions:\n- hono (npm): affected all versions; fixed in 4.6.5\n- hono (npm): affected all versions; fixed in 4.6.5\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-2024-48913/ (Markdown: https://insights.sbomify.com/CVE-2024-48913/index.md)","id":"CVE-2024-48913","markdown":"https://insights.sbomify.com/CVE-2024-48913/index.md","name":"CVE-2024-48913","record":{"aliases":["GHSA-2234-fmw7-43wr","MINI-v678-9c6f-pvw5"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Hono web framework","requires_auth":"none","summary":"Attackers can bypass CSRF protection in the Hono web framework by sending requests without a Content-Type header, allowing unauthorized state-changing actions.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"hono","vendor":"hono"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Hono, a web framework, prior to version 4.6.5 is vulnerable to bypass of cross-site request forgery (CSRF) middleware by a request without Content-Type header. Although the CSRF middleware verifies the Content-Type Header, Hono always considers a request without a Content-Type header to be safe. This can allow an attacker to bypass CSRF protection implemented with Hono CSRF middleware. Version 4.6.5 fixes this issue.","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":"Hono vulnerable to bypass of CSRF Middleware by a request without Content-Type header.","id":"CVE-2024-48913","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":2,"n_references":3,"next":{"headline":"Vendure asset server plugin has local file read vulnerability with AssetServerPlugin \u0026 LocalAssetStorageStrategy","id":"CVE-2024-48914"},"packages":[{"ecosystem":"npm","fixed":["4.6.5"],"introduced":["0"],"last_affected":[],"package":"hono","purl":null,"source":"GHSA-2234-fmw7-43wr"},{"ecosystem":"npm","fixed":["4.6.5"],"introduced":["0"],"last_affected":[],"package":"hono","purl":"pkg:npm/hono","source":"GHSA-2234-fmw7-43wr"}],"prev":{"headline":"GLPI vulnerable to authenticated insecure account deletion","id":"CVE-2024-48912"},"products":["hono"],"published":"2024-10-15","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)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-07","vendors":["honojs"]},"summary":"Attackers can bypass CSRF protection in the Hono web framework by sending requests without a Content-Type header, allowing unauthorized state-changing actions.","url":"https://insights.sbomify.com/CVE-2024-48913/"}