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
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: perl-Date-Manip (AlmaLinux:10) 6.94-5.el10_2.1; perl-Date-Manip (AlmaLinux:8) 6.60-3.el8_10.1; perl-Date-Manip (AlmaLinux:9) 6.85-3.el9_8.1.
Low priority for now. Upgrade to perl-Date-Manip (AlmaLinux:10) 6.94-5.el10_2.1; perl-Date-Manip (AlmaLinux:8) 6.60-3.el8_10.1; perl-Date-Manip (AlmaLinux:9) 6.85-3.el9_8.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Date::Manip versions through 7.00 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.
- EUVD-2026-51125
- ALSA-2026:56970
- ALSA-2026:56971
- ALSA-2026:57562
- openSUSE-SU-2026:11457-1
- openSUSE-SU-2026:21510-1
- openSUSE-SU-2026:21552-1
- RHSA-2026:56970
- RHSA-2026:56971
- RHSA-2026:57562
- RLSA-2026:56970
- RLSA-2026:56971
- RLSA-2026:57562
- SUSE-SU-2026:23218-1
- SUSE-SU-2026:23229-1
- SUSE-SU-2026:3537-1
- SUSE-SU-2026:3551-1
- Published
- Jul 30, 2026
- Updated
- Oct 23, 2026
- EPSS
- 0.3% · 31th percentile
- CWE
- CWE-1333
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (CPANSec). Independent of NVD's CPE analysis and usually ahead of it.
cpan.org/modules Date-Manip
- up to and including 7.00affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | perl-Date-Manip | before 6.94-5.el10_2.1 | 6.94-5.el10_2.1 |
| AlmaLinux:8 | perl-Date-Manip | before 6.60-3.el8_10.1 | 6.60-3.el8_10.1 |
| AlmaLinux:9 | perl-Date-Manip | before 6.85-3.el9_8.1 | 6.85-3.el9_8.1 |
| Debian:12 | libdate-manip-perl | from 0 | — |
| Debian:14 | libdate-manip-perl | before 6.99-2 | 6.99-2 |
| openSUSE:Leap 16.0 | perl-Date-Manip | before 6.980.0-bp160.2.1 | 6.980.0-bp160.2.1 |
| openSUSE:Leap 16.0 | perl-Date-Manip | before 6.960.0-160000.3.1 | 6.960.0-160000.3.1 |
| openSUSE:Tumbleweed | perl-Date-Manip | before 6.990.0-2.1 | 6.990.0-2.1 |
| Red Hat:enterprise_linux:10.2 | perl-Date-Manip | before 0:6.94-5.el10_2.1 | 0:6.94-5.el10_2.1 |
| Red Hat:enterprise_linux:8::baseos | perl-Date-Manip | before 0:6.60-3.el8_10.1 | 0:6.60-3.el8_10.1 |
| Red Hat:enterprise_linux:9::appstream | perl-Date-Manip | before 0:6.85-3.el9_8.1 | 0:6.85-3.el9_8.1 |
| Rocky Linux:10 | perl-Date-Manip | before 0:6.94-5.el10_2.1 | 0:6.94-5.el10_2.1 |
| Rocky Linux:8 | perl-Date-Manip | before 0:6.60-3.el8_10.1 | 0:6.60-3.el8_10.1 |
| Rocky Linux:9 | perl-Date-Manip | before 0:6.85-3.el9_8.1 | 0:6.85-3.el9_8.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP7 | perl-Date-Manip | before 6.70-150000.4.3.1 | 6.70-150000.4.3.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | perl-Date-Manip | before 6.42-3.3.1 | 6.42-3.3.1 |
| SUSE:Linux Enterprise Server 16.0 | perl-Date-Manip | before 6.960.0-160000.3.1 | 6.960.0-160000.3.1 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:perl-Date-Manip | 6.85-3.el9_8.1 · AlmaLinux:9 | Package registry (OSV) |
| debian:libdate-manip-perl | 6.99-2 · Debian:14 | Package registry (OSV) |
| opensuse:perl-Date-Manip | 6.990.0-2.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:perl-Date-Manip | 0:6.85-3.el9_8.1 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| rocky linux:perl-Date-Manip | 0:6.85-3.el9_8.1 · Rocky Linux:9 | Package registry (OSV) |
| suse:perl-Date-Manip | 6.960.0-160000.3.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-1333 · Inefficient Regular Expression ComplexityCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.