CVE-2026-60075

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-30. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 30, 2026

Last Modified

September 2, 2026

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatperl-Date-Manip-0:6.60-3.el8_10.12026-08-20redhat
redhatperl-Date-Manip-0:6.94-5.el10_2.12026-08-19redhat
redhatperl-Date-Manip-0:6.85-3.el9_8.12026-08-19redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libdate-manip-perl6.83-1 ... 6.99-2 (16 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libdate-manip-perl6.91-1 ... 7.00-1 (11 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libdate-manip-perl6.98-1, 6.99-1, 6.99-2, 7.00-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libdate-manip-perl6.98-1, 6.99-1
  • every version up to 6.99-2: fixed in 6.99-2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 22× in last 7d / 117× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 282 total refreshes for this CVE.

  1. 2026-10-04 23:58 UTCEG score recompute
  2. 2026-10-04 23:58 UTCVendor advisory
  3. 2026-10-04 23:58 UTCGHSA enrichment
  4. 2026-10-04 23:22 UTCEPSS rescore
  5. 2026-10-04 06:39 UTCEG score recompute
  6. 2026-10-04 06:39 UTCVendor advisory
  7. 2026-10-04 06:39 UTCGHSA enrichment
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-02 17:56 UTCEPSS rescore
  10. 2026-10-02 16:59 UTCEG score recompute
  11. 2026-10-02 16:59 UTCVendor advisory
  12. 2026-10-02 16:59 UTCGHSA enrichment
  13. 2026-10-01 19:50 UTCEPSS rescore
  14. 2026-10-01 14:44 UTCVendor advisory
  15. 2026-10-01 14:44 UTCGHSA enrichment
  16. 2026-10-01 02:55 UTCEG score recompute
  17. 2026-10-01 02:55 UTCVendor advisory
  18. 2026-10-01 02:55 UTCGHSA enrichment
  19. 2026-09-30 15:03 UTCEPSS rescore
  20. 2026-09-29 06:54 UTCEG score recompute
  21. 2026-09-29 06:54 UTCVendor advisory
  22. 2026-09-29 06:54 UTCGHSA enrichment
  23. 2026-09-28 13:51 UTCEPSS rescore
  24. 2026-09-28 07:10 UTCVendor advisory
  25. 2026-09-28 07:10 UTCGHSA enrichment
Show 75 more
  1. 2026-09-27 19:01 UTCEG score recompute
  2. 2026-09-27 19:01 UTCVendor advisory
  3. 2026-09-27 19:01 UTCGHSA enrichment
  4. 2026-09-26 15:59 UTCEPSS rescore
  5. 2026-09-25 04:57 UTCEG score recompute
  6. 2026-09-25 04:57 UTCVendor advisory
  7. 2026-09-25 04:57 UTCGHSA enrichment
  8. 2026-09-24 09:17 UTCVendor advisory
  9. 2026-09-24 09:17 UTCGHSA enrichment
  10. 2026-09-23 21:31 UTCEG score recompute
  11. 2026-09-23 21:31 UTCVendor advisory
  12. 2026-09-23 21:31 UTCGHSA enrichment
  13. 2026-09-23 17:54 UTCEPSS rescore
  14. 2026-09-23 03:02 UTCEG score recompute
  15. 2026-09-23 03:02 UTCVendor advisory
  16. 2026-09-23 03:02 UTCGHSA enrichment
  17. 2026-09-22 15:15 UTCEG score recompute
  18. 2026-09-22 15:15 UTCVendor advisory
  19. 2026-09-22 15:15 UTCGHSA enrichment
  20. 2026-09-20 21:20 UTCEG score recompute
  21. 2026-09-20 21:20 UTCVendor advisory
  22. 2026-09-20 21:19 UTCGHSA enrichment
  23. 2026-09-20 20:16 UTCEPSS rescore
  24. 2026-09-19 23:48 UTCEG score recompute
  25. 2026-09-19 23:48 UTCVendor advisory
  26. 2026-09-19 23:48 UTCGHSA enrichment
  27. 2026-09-19 04:17 UTCEG score recompute
  28. 2026-09-19 04:17 UTCVendor advisory
  29. 2026-09-19 04:17 UTCGHSA enrichment
  30. 2026-09-18 19:28 UTCEPSS rescore
  31. 2026-09-18 13:36 UTCVendor advisory
  32. 2026-09-18 13:36 UTCGHSA enrichment
  33. 2026-09-18 01:23 UTCEG score recompute
  34. 2026-09-18 01:23 UTCVendor advisory
  35. 2026-09-18 01:23 UTCGHSA enrichment
  36. 2026-09-17 19:31 UTCEPSS rescore
  37. 2026-09-17 01:29 UTCEG score recompute
  38. 2026-09-17 01:29 UTCVendor advisory
  39. 2026-09-17 01:29 UTCGHSA enrichment
  40. 2026-09-16 14:08 UTCEPSS rescore
  41. 2026-09-16 05:36 UTCEG score recompute
  42. 2026-09-16 05:36 UTCVendor advisory
  43. 2026-09-16 05:36 UTCGHSA enrichment
  44. 2026-09-16 05:15 UTCEPSS rescore
  45. 2026-09-15 03:21 UTCEG score recompute
  46. 2026-09-15 03:21 UTCVendor advisory
  47. 2026-09-15 03:21 UTCGHSA enrichment
  48. 2026-09-15 03:11 UTCEPSS rescore
  49. 2026-09-14 14:52 UTCVendor advisory
  50. 2026-09-14 14:52 UTCGHSA enrichment
  51. 2026-09-14 03:05 UTCEG score recompute
  52. 2026-09-14 03:05 UTCVendor advisory
  53. 2026-09-14 03:05 UTCGHSA enrichment
  54. 2026-09-13 16:47 UTCEPSS rescore
  55. 2026-09-13 15:18 UTCVendor advisory
  56. 2026-09-13 15:18 UTCGHSA enrichment
  57. 2026-09-13 02:50 UTCVendor advisory
  58. 2026-09-13 02:50 UTCGHSA enrichment
  59. 2026-09-12 15:02 UTCEG score recompute
  60. 2026-09-12 15:02 UTCVendor advisory
  61. 2026-09-12 15:02 UTCGHSA enrichment
  62. 2026-09-12 03:15 UTCVendor advisory
  63. 2026-09-12 03:15 UTCGHSA enrichment
  64. 2026-09-11 15:27 UTCEG score recompute
  65. 2026-09-11 15:27 UTCVendor advisory
  66. 2026-09-11 15:27 UTCGHSA enrichment
  67. 2026-09-11 14:53 UTCEPSS rescore
  68. 2026-09-11 03:40 UTCVendor advisory
  69. 2026-09-11 03:40 UTCGHSA enrichment
  70. 2026-09-10 15:54 UTCEG score recompute
  71. 2026-09-10 15:54 UTCVendor advisory
  72. 2026-09-10 15:54 UTCGHSA enrichment
  73. 2026-09-10 09:35 UTCEPSS rescore
  74. 2026-09-10 03:34 UTCVendor advisory
  75. 2026-09-10 03:34 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-60075?
CVE-2026-60075 is a high vulnerability published on July 30, 2026. Date::Manip versions through 7.00 for Perl allow CPU exhaustion via quadratic backtracking in the unanchored time substitution in parsetime. parsetime removes a time from anywhere in the string with the unanchored substitution s/$timerx/ /, where $timerx is an auto-generated alternation of time…
When was CVE-2026-60075 disclosed?
CVE-2026-60075 was first published on July 30, 2026, with the most recent update on September 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-60075 actively exploited?
CVE-2026-60075 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-60075?
CVE-2026-60075 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-60075?
A fix for CVE-2026-60075 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-60075 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-60075

Explore →

Is Your Infrastructure Affected by CVE-2026-60075?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.