{"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-62610 in the wild and no public exploit code.","fix":"Upgrade hono to 4.10.2 or later.","what":"CVE-2025-62610 is a high-severity authentication bypass vulnerability in honojs hono, published on 22 Oct 2025. 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-2025-62610 and fix it if it is affected.\n\nWhat it is: CVE-2025-62610 is a high-severity authentication bypass vulnerability in honojs hono, published on 22 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-62610 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- hono (npm): affected from 1.1.0; fixed in 4.10.2\n- hono (npm): affected from 1.1.0; fixed in 4.10.2\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-62610/ (Markdown: https://insights.sbomify.com/CVE-2025-62610/index.md)","id":"CVE-2025-62610","markdown":"https://insights.sbomify.com/CVE-2025-62610/index.md","name":"CVE-2025-62610","record":{"aliases":["GHSA-m732-5p4w-x69g","MINI-w9hf-hr28-6xqm"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript web framework","requires_auth":"none","summary":"Attackers can use tokens issued for other services to gain unauthorized access to APIs using Hono's JWT middleware due to missing audience validation.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"hono","vendor":"hono"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"Hono is a Web application framework that provides support for any JavaScript runtime. In versions from 1.1.0 to before 4.10.2, Hono’s JWT Auth Middleware does not provide a built-in aud (Audience) verification option, which can cause confused-deputy / token-mix-up issues: an API may accept a valid token that was issued for a different audience (e.g., another service) when multiple services share the same issuer/keys. This can lead to unintended cross-service access. Hono’s docs list verification options for iss/nbf/iat/exp only, with no aud support; RFC 7519 requires that when an aud claim is present, tokens MUST be rejected unless the processing party identifies itself in that claim. This issue has been patched in version 4.10.2.","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 Improperly Authorizes JWT Audience Validation","id":"CVE-2025-62610","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"aiomysql allows arbitrary access to client files through vulnerability of a malicious MySQL server","id":"CVE-2025-62611"},"packages":[{"ecosystem":"npm","fixed":["4.10.2"],"introduced":["1.1.0"],"last_affected":[],"package":"hono","purl":null,"source":"GHSA-m732-5p4w-x69g"},{"ecosystem":"npm","fixed":["4.10.2"],"introduced":["1.1.0"],"last_affected":[],"package":"hono","purl":"pkg:npm/hono","source":"GHSA-m732-5p4w-x69g"}],"prev":{"headline":"MLX has Wild Pointer Dereference in load_gguf()","id":"CVE-2025-62609"},"products":["hono"],"published":"2025-10-22","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":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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-23","vendors":["honojs"]},"summary":"Attackers can use tokens issued for other services to gain unauthorized access to APIs using Hono's JWT middleware due to missing audience validation.","url":"https://insights.sbomify.com/CVE-2025-62610/"}