CVE-2026-60075: Date::Manip versions through 7.00 for Perl allow CPU exhaustion via quadratic backtracking in the unanchored time substitution in _parse_time
Date::Manip versions through 6.99 for Perl allow CPU exhaustion via quadratic backtracking in the unanchored time substitution in parsetime.
parsetime 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 ->parsetime() can be made to spend unbounded CPU in a single parse, a denial of service.
Other sources
Date::Manip versions through 7.00 for Perl allow CPU exhaustion via quadratic backtracking in the unanchored time substitution in parsetime.
parsetime 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 ->parsetime() can be made to spend unbounded CPU in a single parse, a denial of service.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Date::Manip (Perl)to a version that resolves this vulnerability.Fixed in 7.00 - Upgrade
Upgrade
Date::Manip (Perl)to a version that resolves this vulnerability.Fixed in 6.99
Event History
Frequently Asked Questions
What is the severity of CVE-2026-60075?
CVE-2026-60075 has a severity rating of high at 7.5 on the CVSS scale.
How does CVE-2026-60075 affect Date::Manip?
CVE-2026-60075 allows for CPU exhaustion due to quadratic backtracking during unanchored time substitutions in the _parse_time function.
What versions of Date::Manip are affected by CVE-2026-60075?
CVE-2026-60075 affects Date::Manip versions through 6.99.
How can I mitigate CVE-2026-60075?
To mitigate CVE-2026-60075, upgrade Date::Manip to a version beyond 6.99 where the vulnerability has been patched.
Who is affected by CVE-2026-60075?
Any users or applications utilizing Date::Manip versions through 6.99 are at risk due to CVE-2026-60075.