PatchTheCVECVE-2021-23371: This affects the package chrono-node before 2.2.4
CVE-2021-23371 is a high-severity flaw (CVSS 7.5) affecting chrono-node. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
This affects the package chrono-node before 2.2.4. It hangs on a date-like string with lots of embedded spaces.
Why this priority
- High severity
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.5 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 2.0% (top 19%) |
| CISA exploited list | No |
| Published | 2021-04-12 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2021-23371?
chrono-node: upgrade to 2.2.4. Exact commands for each OS are on this page.
Is CVE-2021-23371 being exploited?
CVE-2021-23371 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2021-23371 affect?
CVE-2021-23371 affects chrono-node. Severity is high (CVSS 7.5). This affects the package chrono-node before 2.2.4. It hangs on a date-like string with lots of embedded spaces.
How urgent is CVE-2021-23371?
Priority 56/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action