CVE-2023-38039

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2023-09-15. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 62%
CISA-KEV: Not listedEPSS: 62%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API.

However, curl did not have a limit in how many or how large headers it would accept in a response, allowing a malicious server to stream an endless series of headers and eventually cause curl to run out of heap memory.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
EPSS
99.1%
KEV
Not listed

Published

September 15, 2023

Last Modified

December 2, 2025

Vendor Advisories for CVE-2023-38039(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibcurl4-openssl-dev (7.88.1-8ubuntu2.2) @ lunar2026-05-24ubuntu
redhatjbcs-httpd24-curl-0:8.4.0-2.el7jbcs2023-12-07redhat
redhatjbcs-httpd24-curl2023-12-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.

Weakness Classification(1)

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

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 8× in last 7d / 35× 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.

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

Frequently asked(5)

What is CVE-2023-38039?
CVE-2023-38039 is a high vulnerability published on September 15, 2023. When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API. However, curl did not have a limit in how many or how large headers it would accept in a response, allowing a malicious server to stream an endless series of headers…
When was CVE-2023-38039 disclosed?
CVE-2023-38039 was first published in the National Vulnerability Database on September 15, 2023, with the most recent update on December 2, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-38039 actively exploited?
CVE-2023-38039 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-38039?
CVE-2023-38039 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2023-38039?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-38039, 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-2023-38039

Explore →

Is Your Infrastructure Affected by CVE-2023-38039?

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