CVE-2026-14741

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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 (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week

Also known asEUVD-2026-45190 (ENISA EUVD) · GHSA-mcqf-9rr5-v7rw (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • 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.

Fixed versions, as the CVE record's CNA (CPAN Security Group) states them: "Upgrade to HTTP::Date 6.08 or later, which rejects input longer than 64 characters before the date-parsing regexes run."

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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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
49th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 17, 2026

Last Modified

October 24, 2026

Advisory Details (3)

Auto-updated Jul 21, 2026
Patch available. Sources: github_pr.
GitHub pull request

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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibhttp-date-perl (6.06-1ubuntu0.26.04.1) @ resolute2026-10-24ubuntu

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
libhttp-date-perl6.05-1, 6.05-2, 6.06-1, 6.07-1, 6.08-1
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libhttp-date-perl6.05-2, 6.06-1, 6.07-1, 6.08-1
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libhttp-date-perl6.06-1, 6.07-1, 6.08-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libhttp-date-perl6.06-1, 6.07-1
  • every version up to 6.08-1: fixed in 6.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 / 48× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 1,676 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 1,576 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-14741?
CVE-2026-14741 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-14741 published?
The CVE record for CVE-2026-14741 was published on July 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-14741 actively exploited?
CVE-2026-14741 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-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?
A fix for CVE-2026-14741 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (CPAN Security Group) states them: "Upgrade to HTTP::Date 6.08 or later, which rejects input longer than 64 characters before the date-parsing regexes run." The vendor advisories EchelonGraph has for CVE-2026-14741 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-14741

Explore →

Is Your Infrastructure Affected by CVE-2026-14741?

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