---
id: CVE-2025-62610
title: >-
  Hono is a Web application framework that provides support for any JavaScript
  runtime
summary: >-
  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 con…
severity: high
cvss: 8.1
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N'
cwe:
  - CWE-285
vendor: hono
product: hono
affected:
  - 'hono >= 1.1.0, < 4.10.2'
patched:
  - hono 4.10.2
published: '2025-10-22'
updated: '2026-10-08'
sourceUpdated: '2026-10-08T11:10:00.250'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2025-62610'
references:
  - url: >-
      https://github.com/honojs/hono/commit/45ba3bf9e3dff8e4bd85d6b47d4b71c8d6c66bef
    label: security-advisories@github.com
  - url: 'https://github.com/honojs/hono/security/advisories/GHSA-m732-5p4w-x69g'
    label: security-advisories@github.com
tags:
  - nvd
epss: 0.00384
epssPercentile: 0.30336
ingestedAt: '2026-10-08T11:31:27.552Z'
---

## Overview

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

- `hono >= 1.1.0, < 4.10.2`

## Remediation

Upgrade past the affected range:

- `hono 4.10.2`