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%CVSS: 7.5Exploit: None knownExposed: 0

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.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

July 30, 2026

Last Modified

September 2, 2026

Advisory Details (3)

Auto-updated Jul 31, 2026
No patch confirmed yet.

Patch Availability(3)

Vendor / EcosystemFixed in / 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 rangeFixed inDependents
libdate-manip-perl6.83-1 ... 6.99-2 (16 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libdate-manip-perl6.91-1 ... 6.99-2 (10 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libdate-manip-perl6.98-1, 6.99-1, 6.99-2
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libdate-manip-perl6.98-1, 6.99-16.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 32× in last 7d / 142× 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 231 total refreshes for this CVE.

  1. 2026-09-19 04:17 UTCEG score recompute
  2. 2026-09-19 04:17 UTCVendor advisory
  3. 2026-09-19 04:17 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 13:36 UTCVendor advisory
  6. 2026-09-18 13:36 UTCGHSA enrichment
  7. 2026-09-18 01:23 UTCEG score recompute
  8. 2026-09-18 01:23 UTCVendor advisory
  9. 2026-09-18 01:23 UTCGHSA enrichment
  10. 2026-09-17 19:31 UTCEPSS rescore
  11. 2026-09-17 01:29 UTCEG score recompute
  12. 2026-09-17 01:29 UTCVendor advisory
  13. 2026-09-17 01:29 UTCGHSA enrichment
  14. 2026-09-16 14:08 UTCEPSS rescore
  15. 2026-09-16 05:36 UTCEG score recompute
  16. 2026-09-16 05:36 UTCVendor advisory
  17. 2026-09-16 05:36 UTCGHSA enrichment
  18. 2026-09-16 05:15 UTCEPSS rescore
  19. 2026-09-15 03:21 UTCEG score recompute
  20. 2026-09-15 03:21 UTCVendor advisory
  21. 2026-09-15 03:21 UTCGHSA enrichment
  22. 2026-09-15 03:11 UTCEPSS rescore
  23. 2026-09-14 14:52 UTCVendor advisory
  24. 2026-09-14 14:52 UTCGHSA enrichment
  25. 2026-09-14 03:05 UTCEG score recompute
Show 75 more
  1. 2026-09-14 03:05 UTCVendor advisory
  2. 2026-09-14 03:05 UTCGHSA enrichment
  3. 2026-09-13 16:47 UTCEPSS rescore
  4. 2026-09-13 15:18 UTCVendor advisory
  5. 2026-09-13 15:18 UTCGHSA enrichment
  6. 2026-09-13 02:50 UTCVendor advisory
  7. 2026-09-13 02:50 UTCGHSA enrichment
  8. 2026-09-12 15:02 UTCEG score recompute
  9. 2026-09-12 15:02 UTCVendor advisory
  10. 2026-09-12 15:02 UTCGHSA enrichment
  11. 2026-09-12 03:15 UTCVendor advisory
  12. 2026-09-12 03:15 UTCGHSA enrichment
  13. 2026-09-11 15:27 UTCEG score recompute
  14. 2026-09-11 15:27 UTCVendor advisory
  15. 2026-09-11 15:27 UTCGHSA enrichment
  16. 2026-09-11 14:53 UTCEPSS rescore
  17. 2026-09-11 03:40 UTCVendor advisory
  18. 2026-09-11 03:40 UTCGHSA enrichment
  19. 2026-09-10 15:54 UTCEG score recompute
  20. 2026-09-10 15:54 UTCVendor advisory
  21. 2026-09-10 15:54 UTCGHSA enrichment
  22. 2026-09-10 09:35 UTCEPSS rescore
  23. 2026-09-10 03:34 UTCVendor advisory
  24. 2026-09-10 03:34 UTCGHSA enrichment
  25. 2026-09-09 07:16 UTCEG score recompute
  26. 2026-09-09 07:16 UTCVendor advisory
  27. 2026-09-09 07:16 UTCGHSA enrichment
  28. 2026-09-08 22:01 UTCEPSS rescore
  29. 2026-09-07 20:00 UTCEG score recompute
  30. 2026-09-07 20:00 UTCVendor advisory
  31. 2026-09-07 20:00 UTCGHSA enrichment
  32. 2026-09-07 16:01 UTCEPSS rescore
  33. 2026-09-06 18:26 UTCEG score recompute
  34. 2026-09-06 18:26 UTCVendor advisory
  35. 2026-09-06 18:26 UTCGHSA enrichment
  36. 2026-09-06 13:47 UTCEPSS rescore
  37. 2026-09-06 06:39 UTCVendor advisory
  38. 2026-09-06 06:39 UTCGHSA enrichment
  39. 2026-09-05 18:50 UTCEG score recompute
  40. 2026-09-05 18:50 UTCVendor advisory
  41. 2026-09-05 18:50 UTCGHSA enrichment
  42. 2026-09-05 04:54 UTCEG score recompute
  43. 2026-09-05 04:54 UTCVendor advisory
  44. 2026-09-05 04:54 UTCGHSA enrichment
  45. 2026-09-04 11:28 UTCEG score recompute
  46. 2026-09-04 11:28 UTCVendor advisory
  47. 2026-09-04 11:28 UTCGHSA enrichment
  48. 2026-09-04 05:07 UTCEPSS rescore
  49. 2026-09-02 14:12 UTCEPSS rescore
  50. 2026-09-02 13:36 UTCVendor advisory
  51. 2026-09-02 13:35 UTCGHSA enrichment
  52. 2026-09-02 12:36 UTCVendor advisory
  53. 2026-09-02 12:35 UTCGHSA enrichment
  54. 2026-09-01 22:38 UTCEG score recompute
  55. 2026-09-01 22:38 UTCVendor advisory
  56. 2026-09-01 22:38 UTCGHSA enrichment
  57. 2026-09-01 13:54 UTCEPSS rescore
  58. 2026-09-01 04:40 UTCEPSS rescore
  59. 2026-08-31 23:34 UTCVendor advisory
  60. 2026-08-31 23:34 UTCGHSA enrichment
  61. 2026-08-30 22:12 UTCEG score recompute
  62. 2026-08-30 22:12 UTCVendor advisory
  63. 2026-08-30 22:12 UTCGHSA enrichment
  64. 2026-08-30 19:17 UTCEPSS rescore
  65. 2026-08-30 10:25 UTCEG score recompute
  66. 2026-08-30 10:25 UTCVendor advisory
  67. 2026-08-30 10:25 UTCGHSA enrichment
  68. 2026-08-30 01:22 UTCEPSS rescore
  69. 2026-08-29 22:36 UTCEG score recompute
  70. 2026-08-29 22:36 UTCVendor advisory
  71. 2026-08-29 22:35 UTCGHSA enrichment
  72. 2026-08-28 21:42 UTCEPSS rescore
  73. 2026-08-27 20:48 UTCEG score recompute
  74. 2026-08-27 20:48 UTCVendor advisory
  75. 2026-08-27 20:48 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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 68.8% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-60075, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.