CVE-2026-60075
HIGHDescription
Date::Manip versions through 6.99 for Perl allow CPU exhaustion via quadratic backtracking in the unanchored time substitution in _parse_time. _parse_time removes a time from anywhere in the string with the unanchored substitution `s/$timerx/ /`, where $timerx is an auto-generated alternation of time patterns reached through a leading `(?:$atrx|^|\s+)`. The engine therefore retries the match at every position of an interior whitespace run: at each start position the leading `\s+` consumes the rest of the run greedily, the time alternation fails because the run holds no digits, and the engine backtracks a space at a time across the run before advancing the start position, which is quadratic in the length of the run. No time need be present in the string for this to happen, only a long run of whitespace, and the parse time rises about fourfold for each doubling of the run: a few kilobytes of whitespace costs seconds of CPU per parse and tens of kilobytes costs minutes. Any caller that passes an untrusted string of unbounded length to ParseDate(), Date::Manip::Date->parse() or ->parse_time() can be made to spend unbounded CPU in a single parse, a denial of service.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 32% of all known CVEs.
References
Related Vulnerabilities
Other CWE-1333 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-3364 | High | 7.5 | 44% | - | Fix |
| CVE-2024-8124 | High | 7.5 | 40% | - | Fix |
| CVE-2024-25126 | Medium | 5.3 | 35% | - | Fix |
| CVE-2024-2651 | Medium | 6.5 | 33% | - | Fix |
| CVE-2021-32837 | High | 7.5 | 29% | - | Fix |
| CVE-2024-2829 | High | 7.5 | 26% | - | Fix |
Common questions
How do I fix CVE-2026-60075?
Published advisories record a fix for 3 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-60075 being actively exploited?
Not that we know of. CVE-2026-60075 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.39% is the estimated probability that it will be exploited in the next 30 days. That is higher than 32% of all scored CVEs.
How severe is CVE-2026-60075?
CVE-2026-60075 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-60075 affect?
Published advisories record a fix for libdate-manip-perl (Debian), perl-Date-Manip (Red Hat / RHEL), perl-Date-Manip (Rocky). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-60075
Markdown
[](https://tridentstack.com/cve/CVE-2026-60075)HTML
<a href="https://tridentstack.com/cve/CVE-2026-60075"><img src="https://tridentstack.com/cve/badge/CVE-2026-60075.svg" alt="CVE-2026-60075"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-21.