CVE-2026-47673: CWE-285: Improper Authorization in honojs hono
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.21, the jwt and jwk middlewares do not verify that the Authorization header value uses theBearer scheme. Any two-part header value — regardless of the scheme name in the first position — proceeds to JWT verification. A request presenting a valid JWT under a non-Bearer scheme identifier (such as Basic or Token) is authenticated identically to a correctly formed Bearer request. This vulnerability is fixed in 4.12.21.
AI Analysis
Technical Summary
CVE-2026-47673 is an improper authorization vulnerability (CWE-285) in the honojs hono framework affecting versions before 4.12.21. The jwt and jwk middlewares fail to enforce that the Authorization header uses the Bearer scheme, allowing any two-part header value to be processed for JWT verification. Consequently, a valid JWT token presented with a non-Bearer scheme identifier (e.g., Basic or Token) is treated as authenticated. This flaw could lead to unintended authentication bypass scenarios. The vulnerability has a CVSS 3.1 base score of 4.8 (medium severity) and was fixed in version 4.12.21.
Potential Impact
The vulnerability allows an attacker to authenticate using a valid JWT token even if the Authorization header does not use the Bearer scheme, potentially bypassing intended authorization checks. The impact is limited to confidentiality and integrity with no availability impact, and requires network access with high attack complexity and no privileges or user interaction. No known exploits are reported in the wild.
Mitigation Recommendations
Upgrade the honojs hono framework to version 4.12.21 or later, where the jwt and jwk middlewares properly verify that the Authorization header uses the Bearer scheme. Patch status is confirmed by the vendor's fix in 4.12.21. Until upgraded, carefully validate Authorization headers in application code as a temporary mitigation.
CVE-2026-47673: CWE-285: Improper Authorization in honojs hono
Description
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.21, the jwt and jwk middlewares do not verify that the Authorization header value uses theBearer scheme. Any two-part header value — regardless of the scheme name in the first position — proceeds to JWT verification. A request presenting a valid JWT under a non-Bearer scheme identifier (such as Basic or Token) is authenticated identically to a correctly formed Bearer request. This vulnerability is fixed in 4.12.21.
CVSS v3.1
Score 4.8medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-47673 is an improper authorization vulnerability (CWE-285) in the honojs hono framework affecting versions before 4.12.21. The jwt and jwk middlewares fail to enforce that the Authorization header uses the Bearer scheme, allowing any two-part header value to be processed for JWT verification. Consequently, a valid JWT token presented with a non-Bearer scheme identifier (e.g., Basic or Token) is treated as authenticated. This flaw could lead to unintended authentication bypass scenarios. The vulnerability has a CVSS 3.1 base score of 4.8 (medium severity) and was fixed in version 4.12.21.
Potential Impact
The vulnerability allows an attacker to authenticate using a valid JWT token even if the Authorization header does not use the Bearer scheme, potentially bypassing intended authorization checks. The impact is limited to confidentiality and integrity with no availability impact, and requires network access with high attack complexity and no privileges or user interaction. No known exploits are reported in the wild.
Mitigation Recommendations
Upgrade the honojs hono framework to version 4.12.21 or later, where the jwt and jwk middlewares properly verify that the Authorization header uses the Bearer scheme. Patch status is confirmed by the vendor's fix in 4.12.21. Until upgraded, carefully validate Authorization headers in application code as a temporary mitigation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-19T21:10:38.798Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a1871ece29bf47b50124594
Added to database: 05/28/2026, 16:48:44 UTC
Last enriched: 06/04/2026, 20:49:22 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 50
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.