Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

CVE-2021-23371 — chrono-node

HIGHFix: wanasit/chrono@98815b5

CVE-2021-23371 is a high-severity (CVSS 7.5) vulnerability in chrono-node. 2 public exploit references exist, so weaponization risk is real. A fix is available for chrono-node — see the affected versions and patch details below.

Denial of service in chrono-node

Also known asGHSA-hpmr-g4pq-jhgpSNYK-JS-CHRONONODE-1083228
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk
0.00%0.83%1.66%2.49%0.4%2.0%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-23371 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

661other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
chrono-nodenpm
2.1Mdownloads / week

Description

This affects the package chrono-node before 2.2.4. It hangs on a date-like string with lots of embedded spaces.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmchrono-nodeall versions2.2.4npm install chrono-node@2.2.4

Affected Products

1 product · 1 configurations
Application
chrono-nodechrono-node_project
< 2.2.4
range
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

This affects the package chrono-node before 2.2.4. It hangs on a date-li…

github.comNVDApr 2021

This affects the package chrono-node before 2.2.4. It hangs on a date-li…

snyk.ioNVDApr 2021

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for chrono-node, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update chrono-node to 2.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-23371 is resolved across your whole dependency graph.

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

Frequently Asked Questions

This affects the package chrono-node before 2.2.4. It hangs on a date-like string with lots of embedded spaces.
O3 Security · Impact-Aware SCA

Is CVE-2021-23371 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2021-23371: chrono-node — Fixed in 2.2.4