CVE-2025-62610VulnerabilityPublished 22 Oct 2025

CVE-2025-62610: honojs hono · Improper Authorization

Affects honojs honoSource CVE Database V5

Not known to be exploited · CVSS 8.1 High · fixed in 4.10.2 : patch honojs hono soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.10.2

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Upgrade all Hono framework instances to version 4.10.2 or later, where the 'aud' claim verification is implemented and enforced by default. 2. If upgrading immediately is not feasible, implement custom middleware to explicitly validate the 'aud' claim in JWTs against the expected audience for each service, rejecting tokens that do not match. 3. Review and segregate JWT issuers and signing keys per service to minimize token reuse risks across services. 4. Conduct a thorough audit of all services using Hono to identify those sharing issuer and keys and assess exposure. 5. Enhance logging and monitoring to detect anomalous token usage patterns indicative of token mix-up exploitation. 6. Educate development teams on proper JWT validation practices aligned with RFC 7519, emphasizing the importance of audience claim checks. 7. Integrate automated security testing in CI/CD pipelines to verify JWT validation logic correctness. 8. Coordinate with identity providers to ensure tokens issued include correct and consistent 'aud' claims. 9. Prepare incident response plans for potential unauthorized access scenarios stemming from this vulnerability.

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.

Impact

For European organizations, this vulnerability poses a significant risk in environments where multiple services share the same JWT issuer and signing keys but serve different audiences. Attackers can exploit this flaw to gain unauthorized access to services by presenting tokens issued for other services, potentially leading to data breaches, unauthorized actions, and lateral movement within enterprise systems. This can compromise sensitive customer data, intellectual property, and internal APIs, impacting confidentiality and integrity. The risk is particularly acute for organizations adopting microservices architectures or API ecosystems using Hono for authentication. Regulatory compliance frameworks such as GDPR may impose penalties if unauthorized data access occurs. The lack of availability impact reduces the risk of service disruption but does not mitigate the serious confidentiality and integrity concerns. The absence of known exploits suggests a window for proactive mitigation before widespread attacks occur.

Summary

CVE-2025-62610 is an improper authorization vulnerability classified under CWE-285 affecting the Hono JavaScript web framework versions from 1.1.0 up to before 4.10.2. Hono’s JWT Auth Middleware does not natively verify the 'aud' (audience) claim in JSON Web Tokens, which is a critical security check mandated by RFC 7519. The 'aud' claim ensures that a token is accepted only by the intended recipient service. Without this verification, tokens issued for one service can be mistakenly accepted by another service sharing the same issuer and cryptographic keys, leading to confused-deputy or token mix-up attacks. This flaw can allow an attacker to gain unauthorized access to APIs or services by presenting a valid token meant for a different service, thereby compromising confidentiality and integrity of data and operations. The vulnerability does not affect availability and requires user interaction, such as submitting a crafted token. The CVSS v3.1 score is 8.1 (high severity), reflecting network attack vector, low attack complexity, no privileges required, and user interaction needed. The vulnerability was publicly disclosed on October 22, 2025, and patched in Hono version 4.10.2. No known exploits in the wild have been reported yet. Organizations using Hono in multi-service environments must be aware that relying solely on issuer and key validation without audience claim checks is insufficient for secure token validation.

CWE-285Improper Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that you perform access control checks related to your business logic. These checks may be different than the access control checks that you apply to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Cross Zone Scripting (opens in a new tab)
Directory Indexing (opens in a new tab)
Subverting Environment Variable Values (opens in a new tab)
Using Malicious Files (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 29 Oct 2025, 19:55 UTC

WeaknessesCWE-285

Technical details

References

Community reviews

Related threats