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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/honojs/hono/commit/45ba3bf9e3dff8e4bd85d6b47d4b71c8d6c66bef Patch
- https://github.com/honojs/hono/security/advisories/GHSA-m732-5p4w-x69g Exploit, Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.1 · honoNVD modified 2026-10-08 11:10
Affected (CPE criteria) 1
cpe:2.3:a:hono:hono:*:*:*:*:*:node.js:*:*
References 2
- https://github.com/honojs/hono/commit/45ba3bf9e3dff8e4bd85d6b47d4b71c8d6c66bef Patch
- https://github.com/honojs/hono/security/advisories/GHSA-m732-5p4w-x69g Exploit, Mitigation, Vendor Advisory