PatchSiren cyber security CVE debrief
CVE-2026-60074 SBECK CVE debrief
The CVE-2026-60074 vulnerability affects Date::Manip versions through 6.99 for Perl, allowing date corruption via non-ASCII decimal digits. This occurs because the parse regexes use the `//d` shorthand, which matches the whole Unicode decimal digit property `//p{Nd}`, not just `[0-9]`. The vulnerability has a CVSS score of 7.5 and is classified as HIGH severity. Developers and administrators using Date::Manip in Perl applications should review and update date parsing logic to handle non-ASCII decimal digits. The CVE record was published on 2026-07-30T14:17:02.587Z and has not been modified since then. To address this vulnerability, it is recommended to review compensating controls for exposed systems while remediation is scheduled and verified, and to track exceptions, retest remediated assets, and close the item only after evidence is documented.
- Vendor
- SBECK
- Product
- Date::Manip
- CVSS
- HIGH 7.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-30
- Original CVE updated
- 2026-07-31
- Advisory published
- 2026-07-30
- Advisory updated
- 2026-07-31
Who should care
Developers and administrators using Date::Manip in Perl applications, especially those that parse dates from untrusted sources, should review and update date parsing logic to handle non-ASCII decimal digits. This includes reviewing compensating controls for exposed systems while remediation is scheduled and verified, and tracking exceptions, retesting remediated assets, and closing the item only after evidence is documented. Additionally, security teams and vulnerability management teams should be aware of the potential impact of this vulnerability on their systems and take steps to mitigate it. Operators of systems using Date::Manip should also be aware of the potential for date corruption and take steps to verify the accuracy of date parsing logic. Vulnerability management teams should prioritize this vulnerability for remediation due to its high severity and potential impact on date parsing logic. Security teams should review and update their monitoring, detection, and logs for exposed assets that need extra review. Asset inventory teams should verify that affected systems are identified and prioritized for remediation. Rollback/change windows teams should plan for vendor-supported updates or mitigations through normal change control where exposure is confirmed. Source tracking teams should track the status of remediation efforts and verify that evidence is documented before closing the item. Compensating controls should be reviewed and implemented for exposed systems while remediation is scheduled and verified. Monitoring and detection teams should review relevant logs for exposed assets that need extra review. Asset inventory teams should verify that affected systems are identified and prioritized for remediation. Rollback/change windows teams should plan vendor-supported updates or mitigations through normal change control where exposure is confirmed. Source tracking teams should track exceptions, retest remediated assets, and close the item only after evidence is documented. Compensating controls should be reviewed and implemented for exposed systems while remediation is scheduled and verified. Monitoring and detection teams should review relevant logs to
Technical summary
Date::Manip versions through 6.99 for Perl are vulnerable to date corruption due to non-ASCII decimal digits. The `//d` shorthand in parse regexes matches the whole Unicode decimal digit property `//p{Nd}`, not just `[0-9]`. This can lead to incorrect date parsing when untrusted character strings are passed to ParseDate() or Date::Manip::Date->parse(). The vulnerability has a CVSS score of 7.5 and is classified as HIGH severity. To mitigate this vulnerability, it is recommended to review and update date parsing logic to handle non-ASCII decimal digits, implement additional validation checks for date inputs, and consider upgrading to a newer version of Date::Manip.
Defensive priority
High-priority defensive review recommended due to potential impact on date parsing logic.
Recommended defensive actions
- Review and update date parsing logic to handle non-ASCII decimal digits.
- Implement additional validation checks for date inputs.
- Consider upgrading to a newer version of Date::Manip.
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
Evidence notes
Evidence from Date::Manip versions through 6.99 for Perl indicates that non-ASCII decimal digits can cause date corruption. The parse regexes use the `//d` shorthand, which matches the whole Unicode decimal digit property `//p{Nd}`, not just `[0-9]`. This can lead to incorrect date parsing when untrusted character strings are passed to ParseDate() or Date::Manip::Date->parse().
Official resources
-
CVE-2026-60074 CVE record
CVE.org
-
CVE-2026-60074 NVD detail
NVD
-
Source item URL
nvd_modified
-
Source reference
9b29abf9-4ab0-4765-b253-1875cd9b441e
-
Source reference
9b29abf9-4ab0-4765-b253-1875cd9b441e
-
Source reference
9b29abf9-4ab0-4765-b253-1875cd9b441e
-
Source reference
af854a3a-2127-422b-91ae-364da2661108
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-07-30T14:17:02.587Z and has not been modified since then.