Date::Manip up to 6.99 Date Parsing Logic Date->parse incorrect regex

Summaryinfo

A vulnerability identified as critical has been detected in Date::Manip up to 6.99. Affected by this vulnerability is the function ParseDate/Date::Manip::Date->parse of the component Date Parsing Logic. Performing a manipulation results in incorrect regex. This vulnerability was named CVE-2026-60074. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability classified as critical has been found in Date::Manip up to 6.99. This affects the function ParseDate/Date::Manip::Date->parse of the component Date Parsing Logic. The manipulation with an unknown input leads to a incorrect regex vulnerability. CWE is classifying the issue as CWE-185. The product specifies a regular expression in a way that causes data to be improperly matched or compared. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Date::Manip versions through 6.99 for Perl return corrupted dates via non-ASCII decimal digits that pass the numeric range tests in check. The parse regexes capture year, month and day with the `\d` shorthand, which on a character string matches the whole Unicode decimal digit property `\p{Nd}` and not just `[0-9]`. Date::Manip::Base::check then validates the captured fields with numeric comparisons alone (`$y<1 || $y>9999`, `$m<1 || $m>12`, `$d<1 || $d>$days`), and _parse_check stores the numified fields (`$y+0`). Perl truncates a string at the first character that is not an ASCII digit, so a field whose leading characters are ASCII digits numifies to an in-range prefix and satisfies every test: a year field of three ASCII digits followed by U+0664 ARABIC-INDIC DIGIT FOUR numifies to 202, giving the year 0202, and one non-ASCII digit in the month or day field shifts those fields the same way. The hour, minute and second fields match explicit ASCII character classes (`0?[0-9]`, `[0-5][0-9]`) and do not shift, though a non-ASCII digit in a fractional hour or minute field truncates the fraction. Any caller that passes an untrusted character string to ParseDate() or Date::Manip::Date->parse() can get back a date that differs from the string it parsed, with no parse error. Where the parsed date gates logic such as an expiry check or a retention window, the shift goes unnoticed.

The advisory is shared at security.metacpan.org. This vulnerability is uniquely identified as CVE-2026-60074 since 07/08/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/30/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Date::Manip

Version

• 6.0
• 6.1
• 6.2
• 6.3
• 6.4
• 6.5
• 6.6
• 6.7
• 6.8
• 6.9
• 6.10
• 6.11
• 6.12
• 6.13
• 6.14
• 6.15
• 6.16
• 6.17
• 6.18
• 6.19
• 6.20
• 6.21
• 6.22
• 6.23
• 6.24
• 6.25
• 6.26
• 6.27
• 6.28
• 6.29
• 6.30
• 6.31
• 6.32
• 6.33
• 6.34
• 6.35
• 6.36
• 6.37
• 6.38
• 6.39
• 6.40
• 6.41
• 6.42
• 6.43
• 6.44
• 6.45
• 6.46
• 6.47
• 6.48
• 6.49
• 6.50
• 6.51
• 6.52
• 6.53
• 6.54
• 6.55
• 6.56
• 6.57
• 6.58
• 6.59
• 6.60
• 6.61
• 6.62
• 6.63
• 6.64
• 6.65
• 6.66
• 6.67
• 6.68
• 6.69
• 6.70
• 6.71
• 6.72
• 6.73
• 6.74
• 6.75
• 6.76
• 6.77
• 6.78
• 6.79
• 6.80
• 6.81
• 6.82
• 6.83
• 6.84
• 6.85
• 6.86
• 6.87
• 6.88
• 6.89
• 6.90
• 6.91
• 6.92
• 6.93
• 6.94
• 6.95
• 6.96
• 6.97
• 6.98
• 6.99

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion