CVE-2026-14741

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH 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 — 5 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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(high)
EG Risk
34(Track)
EG Risk 34/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%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
46.1%
KEV
Not listed

Published

July 17, 2026

Last Modified

July 21, 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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 1388× in last 7d / 1388× 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,388 total refreshes for this CVE.

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

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 July 21, 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 46.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.