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

CVE-2020-26289 — date-and-time

HIGHFix: knowledgecode/date-and-time@9e4b501

CVE-2020-26289 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in date-and-time. A fix is available for date-and-time — see the affected versions and patch details below.

regular expression denial of service (ReDoS)

Also known asGHSA-r92x-f52r-x54g
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk
0.03%0.91%1.79%2.67%0.5%2.2%Apr 26Aug 26Oct 26

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

How urgent is this, really

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

Where this sits among everything scored

Of 385,987 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.

332other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
date-and-timenpm
388Kdownloads / week

Description

date-and-time is an npm package for manipulating date and time. In date-and-time before version 0.14.2, there a regular expression involved in parsing which can be exploited to to cause a denial of service. This is fixed in version 0.14.2.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmdate-and-timeall versions0.14.2npm install date-and-time@0.14.2

Affected Products

1 product · 1 configurations
Application
date-and-timedate-and-time_project
< 0.14.2
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update date-and-time to 0.14.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-26289 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
Red Hat OpenShift Container Storage 4.7.0 on RHEL-8ocs4/mcg-core-rhel8:5.7.0-60.2c1fdb0.5.7RHSA-2021:2041

Frequently Asked Questions

date-and-time is an npm package for manipulating date and time. In date-and-time before version 0.14.2, there a regular expression involved in parsing which can be exploited to to cause a denial of service. This is fixed in version 0.14.2.
O3 Security · Impact-Aware SCA

Is CVE-2020-26289 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2020-26289: date-and-time DoS — Fixed in 0.14.2