All reports
High

perl-Date-Manip: Date::Manip for Perl: Denial of Service via CPU exhaustion in date parsing

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-60075

Probability of exploitation in the next 30 days: 0.37%

FIRST EPSS · 2026-11-21

Description

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.

A flaw was found in Date::Manip for Perl. An attacker could exploit a vulnerability in the _parse_time function by providing a specially crafted input string containing long sequences of whitespace. This could lead to excessive CPU consumption due to inefficient processing, resulting in a Denial of Service (DoS) for the affected system.