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.
References
| Link | Resource |
|---|---|
| https://github.com/honojs/hono/commit/45ba3bf9e3dff8e4bd85d6b47d4b71c8d6c66bef | Patch |
| https://github.com/honojs/hono/security/advisories/GHSA-m732-5p4w-x69g | Exploit Mitigation Vendor Advisory |
Configurations
History
No history.
Information
Published : 2025-10-22 20:15
Updated : 2026-02-04 15:56
NVD link : CVE-2025-62610
Mitre link : CVE-2025-62610
CVE.ORG link : CVE-2025-62610
JSON object : View
Products Affected
hono
- hono
CWE
CWE-285
Improper Authorization
