CVE-2026-44459
Hono has improper validation of NumericDate claims (exp, nbf, iat) in JWT verify()
Overview
Description
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.18, improper validation of the JWT NumericDate claims exp, nbf, and iat in hono/utils/jwt allows tokens with non-spec-compliant claim values to silently bypass time-based checks. This issue is not exploitable by an anonymous attacker; it only manifests when a malformed claim value reaches verify() — typically when the application itself issues such tokens, or when the signing key is otherwise under attacker control. This vulnerability is fixed in 4.12.18.
Source: OX vulnerability database
Severity
3.8 · LOW
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N
Weakness: CWE-1284
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| npm | hono | <4.12.18 | 4.12.18 |
Open a package to see all its vulnerabilities.
Operating systems · 22 fixes
chainguard 1 release · 14 packages
| Release | Package | Fixed in |
|---|---|---|
| hono | not affected | |
| librechat | 0.8.4-r6 | |
| commercial-gitlab-rails-ee-19-1 | 19.1.7-r3 | |
| commercial-gitlab-rails-ee-fips-19-1 | 19.1.9-r0 | |
| commercial-gitlab-rails-ee-19-2 +1 | 19.2.7-r1 | |
| commercial-gitlab-rails-ee-19-3 +1 | 19.3.3-r1 |
8 more rows
minimos 1 release · 7 packages
| Release | Package | Fixed in |
|---|---|---|
| opensearch-dashboards-2 +1 | 2.19.6-r0 | |
| openclaw | 2026.5.12-r0 | |
| mcp-filesystem | 2026.6.16-r0 | |
| mcp-mongodb | 3.1.0-r0 | |
| trigger-dev | 4.5.4-r0 | |
| kibana-9-3 | 9.3.5-r0 |
1 more row
wolfi 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| langfuse-3 | 3.176.0-r0 |
References
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.