npm
CVE-2026-47673
Hono: JWT middleware accepts any Authorization scheme, not only Bearer
- Severity
- Medium 4.8
- Published
- 4 Jun 2026
- Last changed
- 10 Sept 2026
- Added to UpHeron
- 22 Oct 2026
- Fixed in
- 4.12.21
- Exploit chance
- 0.2% in the next 30 daysHigher than 9% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- Improper authorization (CWE-285)
- Attack
- Over the network · Only under certain conditions · No login needed · No user action needed
- Attacker can
- Read some data · Change some data
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N- Also known as
- GHSA-f577-qrjj-4474
- Sources
- OSV.dev and GitHub
Description
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.
When processing an Authorization (or custom) header, the middleware splits the value on whitespace and uses the second token as the JWT to verify. It does not check that the first token is bearer (case-insensitively). RFC 6750 specifies that JWT bearer tokens must be presented using the Bearer scheme; other scheme identifiers carry distinct semantics and may be subject to different policies in network-layer security controls.
This discrepancy means that scheme-aware external controls — such as WAF rules, API gateways, or reverse proxies that apply policies specific to the Bearer scheme identifier — can be bypassed…
Affected software
| Software | Affected versions |
|---|---|
hononpm · osv:npm:hono |
|
About hono
- Weekly downloads (npm)
- 108,805,821npm, 16 Nov 2026
Vulnerabilities in hono
- In our list
- 26
- Published in the last 12 months
- 26
- Critical, last 12 months
- 0
- High, last 12 months
- 1
- Known exploited
- 0
- CVE-2026-109955Hono: `serveStatic` decodes the request path a second time, leading to bypass of middleware on static pathsMedium 5.3 20 Oct 2026
- CVE-2026-93981hono/jsx renders plain strings unescaped in boundary components, leading to XSSMedium 4.7 30 Sept 2026
- CVE-2026-84365Hono: Incomplete fix for CVE-2026-39408: `toSSG()` still writes files outside the output directoryMedium 6.5 8 Sept 2026
- CVE-2026-84364Hono: Unbounded dot-notation nesting in `parseBody()` can cause memory exhaustionMedium 5.3 8 Sept 2026
- CVE-2026-84363Hono: Query parser reads parameters after the URL fragment, causing cache-key and proxy interpretation differentialsMedium 5.9 8 Sept 2026
- CVE-2026-71850Hono: `memo()` retains SSR output across requests, leading to cross-user data disclosureMedium 4.8 7 Aug 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-47673
- GitHub Advisory Database https://github.com/advisories/GHSA-f577-qrjj-4474