CVE-2025-62610: Hono Improperly Authorizes JWT Audience Validation

Severity: high (CVSS 8.1 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.4% probability of exploitation in the next 30 days
Public exploit or detection template: yes
Published: 2025-10-22 · updated 2026-10-08
Weakness: CWE-285

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.

Affected products

honojs hono: from 1.1.0 before 4.10.2 — fixed in 4.10.2

How to fix

Upgrade to a fixed version: honojs hono 4.10.2. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2025-62610 or the next vulnerability affects your stack