CVE-2024-11053

CRITICALNVD 3.49.1
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2024-12-11. NVD baseline CVSS 3.4; sources differ by 5.7.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2024-34411 (ENISA EUVD) · GHSA-h288-5fq8-5pfw (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 2.0%CVSS: 3.4Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

When asked to both use a .netrc file for credentials and to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances.

This flaw only manifests itself if the netrc file has an entry that matches the redirect target hostname but the entry either omits just the password or omits both login and password.

CVSS v3
3.4
EG Score
9.1CRITICALmedium confidence
EG Risk
57
EG Risk 57/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
2.0%
EPSS %ILE
80th
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 (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
2.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

December 11, 2024

Last Modified

October 15, 2026

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibcurl4-openssl-dev (7.58.0-2ubuntu3.24+esm10) @ bionic2026-11-12ubuntu
ubuntulibcurl4t64 (8.9.1-2ubuntu2.2) @ oracular2026-11-12ubuntu
redhatmysql-0:8.0.41-2.el9_52025-02-19redhat
redhatmysql:8.0-8100020250212154709.489197e62025-02-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

(10 across 10 ecosystems)
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.76.0 up to 8.11.1-r0: fixed in 8.11.1-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.76.0 up to 8.11.1-r0: fixed in 8.11.1-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.76.0 up to 8.11.1-r0: fixed in 8.11.1-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.76.0 up to 8.11.1-r0: fixed in 8.11.1-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.76.0 up to 8.11.1-r0: fixed in 8.11.1-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.76.0 up to 8.11.1-r0: fixed in 8.11.1-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.76.0 up to 8.11.1-r0: fixed in 8.11.1-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
curl7.88.1-10 ... 7.88.1-10+deb12u9 (14 versions)
  • every version up to 7.88.1-10+deb12u10: fixed in 7.88.1-10+deb12u10
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 8.11.1-1: fixed in 8.11.1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 8.11.1-1: fixed in 8.11.1-1
—

Additional Vendor Advisories

(2)

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 20× in last 7d / 90× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 319 rows 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 219 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-11053?
CVE-2024-11053 is a critical-severity vulnerability; its CVE record was published on December 11, 2024. When asked to both use a .netrc file for credentials and to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances. This flaw only manifests itself if the netrc file has an entry that matches the redirect target hostname but…
When was the CVE record for CVE-2024-11053 published?
The CVE record for CVE-2024-11053 was published on December 11, 2024. 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 15, 2026; the record at its source may have been updated since.
Is CVE-2024-11053 actively exploited?
CVE-2024-11053 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.0% probability of exploitation in the next 30 days (80th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-11053?
CVE-2024-11053 has a CVSS v3 base score of 3.4 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.1 (CRITICAL).
How do I remediate CVE-2024-11053?
A fix for CVE-2024-11053 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-11053 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-2024-11053

Explore →

Is Your Infrastructure Affected by CVE-2024-11053?

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