Skip to main content
CVE-2026-60074VulnerabilityPublished Updated

SUSE · Security update for perl-Date-Manip

Affects SUSESource GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-60074· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
CPANDate-Manippkg:cpan/Date-ManipOther threatsAffected
  • <=7.00
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the security update provided by the SUSE Product Security Team for perl-Date-Manip to remediate these vulnerabilities. Since this is an official security update, installing the patch will resolve the issues. No additional mitigations are specified.

Description

This security update for perl-Date-Manip addresses two vulnerabilities: CVE-2026-60074, which causes corrupted dates when processing non-ASCII decimal digits that pass numeric range checks, and CVE-2026-60075, which leads to CPU exhaustion due to quadratic backtracking in the unanchored time substitution in the _parse_time function. Both issues have been fixed in this update.

References

Community reviews

Loading reviews…