CVE-2026-60075

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH 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 — Patch released 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 6.99 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(high)
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
32%
KEV
Not listed

Published

July 30, 2026

Last Modified

July 31, 2026

Advisory Details (3)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
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.

Data Freshness Timeline

(refreshed 28× in last 7d / 92× 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.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 21:23 UTCVendor advisory
  3. 2026-08-20 21:23 UTCGHSA enrichment
  4. 2026-08-20 09:36 UTCVendor advisory
  5. 2026-08-20 09:36 UTCGHSA enrichment
  6. 2026-08-19 21:50 UTCEG score recompute
  7. 2026-08-19 21:50 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 10:03 UTCGHSA enrichment
  10. 2026-08-18 22:15 UTCEG score recompute
  11. 2026-08-18 22:15 UTCGHSA enrichment
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-18 10:28 UTCGHSA enrichment
  14. 2026-08-17 22:40 UTCEG score recompute
  15. 2026-08-17 22:40 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 10:53 UTCGHSA enrichment
  18. 2026-08-16 23:07 UTCEG score recompute
  19. 2026-08-16 23:07 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 11:20 UTCEG score recompute
  22. 2026-08-16 11:20 UTCGHSA enrichment
  23. 2026-08-15 23:34 UTCGHSA enrichment
  24. 2026-08-15 11:47 UTCEG score recompute
  25. 2026-08-15 11:47 UTCGHSA enrichment
Show 67 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-15 00:00 UTCGHSA enrichment
  3. 2026-08-14 12:13 UTCGHSA enrichment
  4. 2026-08-14 00:27 UTCEG score recompute
  5. 2026-08-14 00:27 UTCGHSA enrichment
  6. 2026-08-13 22:00 UTCEPSS rescore
  7. 2026-08-13 12:40 UTCGHSA enrichment
  8. 2026-08-13 00:53 UTCEG score recompute
  9. 2026-08-13 00:53 UTCGHSA enrichment
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-12 13:07 UTCGHSA enrichment
  12. 2026-08-12 01:20 UTCEG score recompute
  13. 2026-08-12 01:20 UTCGHSA enrichment
  14. 2026-08-11 13:34 UTCGHSA enrichment
  15. 2026-08-11 01:47 UTCEG score recompute
  16. 2026-08-11 01:47 UTCGHSA enrichment
  17. 2026-08-11 00:00 UTCEPSS rescore
  18. 2026-08-10 14:00 UTCGHSA enrichment
  19. 2026-08-10 02:14 UTCGHSA enrichment
  20. 2026-08-09 14:27 UTCEG score recompute
  21. 2026-08-09 14:27 UTCGHSA enrichment
  22. 2026-08-09 13:46 UTCEPSS rescore
  23. 2026-08-09 02:41 UTCEG score recompute
  24. 2026-08-09 02:41 UTCGHSA enrichment
  25. 2026-08-08 16:37 UTCEPSS rescore
  26. 2026-08-08 14:55 UTCGHSA enrichment
  27. 2026-08-08 03:08 UTCEG score recompute
  28. 2026-08-08 03:08 UTCGHSA enrichment
  29. 2026-08-07 15:21 UTCGHSA enrichment
  30. 2026-08-07 03:34 UTCGHSA enrichment
  31. 2026-08-06 15:47 UTCEG score recompute
  32. 2026-08-06 15:47 UTCGHSA enrichment
  33. 2026-08-06 13:47 UTCEPSS rescore
  34. 2026-08-06 04:00 UTCEG score recompute
  35. 2026-08-06 04:00 UTCGHSA enrichment
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-05 16:13 UTCGHSA enrichment
  38. 2026-08-05 04:25 UTCGHSA enrichment
  39. 2026-08-04 16:34 UTCEG score recompute
  40. 2026-08-04 16:34 UTCGHSA enrichment
  41. 2026-08-04 15:10 UTCEPSS rescore
  42. 2026-08-04 10:39 UTCEPSS rescore
  43. 2026-08-04 04:48 UTCGHSA enrichment
  44. 2026-08-03 17:01 UTCEG score recompute
  45. 2026-08-03 17:01 UTCGHSA enrichment
  46. 2026-08-03 10:36 UTCEPSS rescore
  47. 2026-08-03 05:14 UTCGHSA enrichment
  48. 2026-08-02 17:26 UTCGHSA enrichment
  49. 2026-08-02 05:39 UTCEG score recompute
  50. 2026-08-02 05:39 UTCGHSA enrichment
  51. 2026-08-02 02:27 UTCEPSS rescore
  52. 2026-08-01 17:53 UTCGHSA enrichment
  53. 2026-08-01 06:06 UTCEG score recompute
  54. 2026-08-01 06:06 UTCGHSA enrichment
  55. 2026-08-01 04:16 UTCEPSS rescore
  56. 2026-07-31 18:20 UTCGHSA enrichment
  57. 2026-07-31 18:04 UTCEG score recompute 7.50
  58. 2026-07-31 18:04 UTCGHSA enrichment
  59. 2026-07-31 18:03 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  60. 2026-07-30 19:12 UTCGHSA enrichment
  61. 2026-07-30 17:26 UTCGHSA enrichment
  62. 2026-07-30 17:23 UTCNVD update
  63. 2026-07-30 16:52 UTCGHSA enrichment
  64. 2026-07-30 16:46 UTCMITRE cvelistV5
  65. 2026-07-30 14:27 UTCNVD update
  66. 2026-07-30 14:06 UTCEG score recompute
  67. 2026-07-30 14:06 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-60075?
CVE-2026-60075 is a high vulnerability published on July 30, 2026. Date::Manip versions through 6.99 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 July 31, 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 67.9% 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.