No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Sat, 30 May 2026 02:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 29 May 2026 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Hono
Hono hono |
|
| CPEs | cpe:2.3:a:hono:hono:*:*:*:*:*:node.js:*:* | |
| Vendors & Products |
Hono
Hono hono |
Thu, 28 May 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Hono: JWT middleware accepts any Authorization scheme, not only Bearer | |
| Weaknesses | CWE-285 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-30T01:59:15.167Z
Reserved: 2026-05-19T21:10:38.798Z
Link: CVE-2026-47673
Updated: 2026-05-30T01:59:10.543Z
Status : Analyzed
Published: 2026-05-28T17:16:32.233
Modified: 2026-05-29T17:05:59.723
Link: CVE-2026-47673
No data.
OpenCVE Enrichment
Updated: 2026-05-28T19:15:06Z