How severe is GHSA-hm8q-7f3q-5f36?

GHSA-hm8q-7f3q-5f36 has a CVSS score of 3.8/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-hm8q-7f3q-5f36?

GHSA-hm8q-7f3q-5f36 affects the following packages: hono (npm). Ecosystems affected: npm.

How do I fix GHSA-hm8q-7f3q-5f36?

Update hono to 4.12.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hm8q-7f3q-5f36 is resolved across your whole dependency graph.

How do I detect GHSA-hm8q-7f3q-5f36 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hono. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-hm8q-7f3q-5f36 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-hm8q-7f3q-5f36?

O3 pinpoints whether GHSA-hm8q-7f3q-5f36 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-hm8q-7f3q-5f36 actively exploited in the wild?

No public exploit code has been indexed for GHSA-hm8q-7f3q-5f36 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-hm8q-7f3q-5f36?

GHSA-hm8q-7f3q-5f36 is classified as CWE-1284 (CWE-1284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hm8q-7f3q-5f36 published, and has it been updated?

GHSA-hm8q-7f3q-5f36 was published on May 9, 2026 and was last updated on May 14, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-hm8q-7f3q-5f36

LOW

GHSA-hm8q-7f3q-5f36 is a low-severity (CVSS 3.8) CWE-1284 vulnerability in hono. O3 Security confirms whether GHSA-hm8q-7f3q-5f36 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Hono has improper validation of NumericDate claims (exp, nbf, iat) in JWT verify()

Also known asCVE-2026-44459

Published

May 9, 2026

Updated

May 14, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

hononpm

56.6Mdownloads / week

Description

Summary

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.

Details

The validation routine combined option, presence, and threshold checks in a single short-circuiting expression, so several classes of malformed values were silently skipped instead of rejected:

A falsy numeric value short-circuited the presence check.
A non-finite numeric value compared as never-after-now and never-expired.
A non-numeric type produced NaN comparisons that evaluated false.

This deviates from RFC 7519 §4.1.4, which defines NumericDate as a finite JSON numeric value.

Impact

An actor able to issue tokens accepted by the application may craft tokens whose exp, nbf, or iat claims silently bypass time-based enforcement. This may lead to:

Tokens treated as never expiring even with exp configured on the verifier.
Tokens with a future nbf accepted as currently valid.
Tokens with a future iat accepted as legitimately issued.

Deployments using a well-formed token issuer and protecting the signing key are not affected.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`hono`	all versions	4.12.18

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hono. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update hono to 4.12.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hm8q-7f3q-5f36 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-hm8q-7f3q-5f36 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-hm8q-7f3q-5f36. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary 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. ### Details The validation routine combined option, presence, and threshold checks in a single short-circuiting expression, so several classes of malformed val

O3 Security · Impact-Aware SCA

Is GHSA-hm8q-7f3q-5f36 in your dependencies?

O3 detects GHSA-hm8q-7f3q-5f36 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works