Hono: Improper validation of NumericDate claims (exp, nbf, iat) in JWT verify()
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| honojs | hono | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Hono | Hono |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-hm8q-7f3q-5f36 | Hono has improper validation of NumericDate claims (exp, nbf, iat) in JWT verify() |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.216% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| 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 |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Hono: Improper validation of NumericDate claims (exp, nbf, iat) in JWT verify() | |
| Weaknesses | CWE-1284 | |
| References |
| |
| Metrics |
cvssV3_1
|