CVE-2026-14741

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-17. 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.

HTTP::Date versions before 6.08 for Perl allow CPU exhaustion via polynomial regex backtracking in parse_date.

parse_date() matches the date string against a chain of alternative regexes, and str2time() delegates to it. Several of these patterns place unbounded quantifiers next to each other before a trailing \s*$ anchor. A valid date prefix followed by a long interior run of digits, letters, or whitespace and a single trailing byte that defeats the final match forces the engine to repartition the run, giving polynomial (about quadratic) backtracking. A header value of a few tens of kilobytes runs for tens of seconds of CPU.

HTTP::Date parses timestamps such as HTTP Date, Expires, and Last-Modified headers, which commonly originate from untrusted sources. Any caller that passes an untrusted date header to str2time() or parse_date() can be driven to consume unbounded CPU, 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
29%
KEV
Not listed

Published

July 17, 2026

Last Modified

August 12, 2026

Advisory Details (3)

Auto-updated Jul 21, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
github_pr

Fix ReDoS in parse_date

Fix merged in libwww-perl/HTTP-Date PR #33 on 2026-07-09 — awaiting tagged release

https://github.com/libwww-perl/HTTP-Date/pull/33

Vendor Advisories for CVE-2026-14741(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibhttp-date-perl (6.06-1ubuntu0.26.04.1) @ resolute2026-09-08ubuntu

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
libhttp-date-perl6.05-1, 6.05-2, 6.06-1, 6.07-1, 6.08-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libhttp-date-perl6.05-2, 6.06-1, 6.07-1, 6.08-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libhttp-date-perl6.06-1, 6.07-1, 6.08-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libhttp-date-perl6.06-1, 6.07-16.08-1

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 14× in last 7d / 115× 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 1,596 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-14741?
CVE-2026-14741 is a high vulnerability published on July 17, 2026. HTTP::Date versions before 6.08 for Perl allow CPU exhaustion via polynomial regex backtracking in parse_date. parse_date() matches the date string against a chain of alternative regexes, and str2time() delegates to it. Several of these patterns place unbounded quantifiers next to each other before…
When was CVE-2026-14741 disclosed?
CVE-2026-14741 was first published in the National Vulnerability Database on July 17, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14741 actively exploited?
CVE-2026-14741 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 71.5% of all scored CVEs.
What is the CVSS score of CVE-2026-14741?
CVE-2026-14741 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-14741?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14741, 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-14741

Explore →

Is Your Infrastructure Affected by CVE-2026-14741?

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