Medium severity · published Jan 13, 2026
CVE-2026-22818
JWT algorithm confusion in Hono JWK Auth Middleware when JWK lacks "alg" (untrusted header.alg fallback)
6.5
CVSS
0.1%
EPSS
No
On KEV
Description
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.11.4, there is a flaw in Hono’s JWK/JWKS JWT verification middleware allowed the algorithm specified in the JWT header to influence signature verification when the selected JWK did not explicitly define an algorithm. This could enable JWT algorithm confusion and, in certain configurations, allow forged tokens to be accepted. The JWK/JWKS JWT verification middleware has been updated to require an explicit allowlist of asymmetric algorithms when verifying tokens. The middleware no longer derives the verification algorithm from untrusted JWT header values. This vulnerability is fixed in 4.11.4.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
Low
Integrity
Low
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.1% · higher than 3% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
HO
hono · honojs
< 4.11.4 · source: vendor, NVD
Affected product
HO
hono
honojs
More from hono
9.8
CVE-2026-29045
Hono: Arbitrary file access via serveStatic vulnerability
8.1
CVE-2025-62610
Hono Improperly Authorizes JWT Audience Validation
7.5
CVE-2026-39408
Hono has a path traversal in toSSG() allows writing files outside the output directory
7.5
CVE-2026-27700
Hono is Vulnerable to Authentication Bypass by IP Spoofing in AWS Lambda ALB conninfo
7.5
CVE-2025-58362
Hono contains a flaw in URL path parsing, potentially leading to path confusion