CVE-2024-2466

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2024-03-27. NVD baseline CVSS 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1.3%CVSS: 6.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

libcurl did not check the server certificate of TLS connections done to a host specified as an IP address, when built to use mbedTLS. libcurl would wrongly avoid using the set hostname function when the specified hostname was given as an IP address, therefore completely skipping the certificate check. This affects all uses of TLS protocols (HTTPS, FTPS, IMAPS, POPS3, SMTPS, etc).

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100CISA SSVC

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
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.3%
EPSS %ILE
70th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

March 27, 2024

Last Modified

July 30, 2025

References (23)

Vendor Advisories for CVE-2024-2466(3)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatjbcs-httpd24-nghttp2-0:1.43.0-13.el7jbcs2024-05-07redhat
redhatjbcs-httpd24-curl2024-05-07redhat

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.17(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 8.5.0 up to 8.7.1-r0: fixed in 8.7.1-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 8.5.0 up to 8.7.1-r0: fixed in 8.7.1-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 8.5.0 up to 8.7.1-r0: fixed in 8.7.1-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 8.5.0 up to 8.7.1-r0: fixed in 8.7.1-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 8.5.0 up to 8.7.1-r0: fixed in 8.7.1-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 8.5.0 up to 8.7.1-r0: fixed in 8.7.1-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 8.5.0 up to 8.7.1-r0: fixed in 8.7.1-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 8.5.0 up to 8.7.1-r0: fixed in 8.7.1-r0
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 8.7.1-1: fixed in 8.7.1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 8.7.1-1: fixed in 8.7.1-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-2466?
CVE-2024-2466 is a medium vulnerability published on March 27, 2024. libcurl did not check the server certificate of TLS connections done to a host specified as an IP address, when built to use mbedTLS. libcurl would wrongly avoid using the set hostname function when the specified hostname was given as an IP address, therefore completely skipping the certificate…
When was CVE-2024-2466 disclosed?
CVE-2024-2466 was first published on March 27, 2024, with the most recent update on July 30, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-2466 actively exploited?
CVE-2024-2466 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% probability of exploitation in the next 30 days (70th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-2466?
CVE-2024-2466 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2024-2466?
A fix for CVE-2024-2466 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-2466 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-2466

Explore →

Is Your Infrastructure Affected by CVE-2024-2466?

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

Book a Demo →Browse All CVEs