CVE-2018-1000005

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-14. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 5%CVSS: 9.1Exploit: None knownExposed: 0

A fix is available — apply it.

libcurl 7.49.0 to and including 7.57.0 contains an out bounds read in code handling HTTP/2 trailers. It was reported (https://github.com/curl/curl/pull/2231) that reading an HTTP/2 trailer could mess up future trailers since the stored size was one byte less than required. The problem is that the code that creates HTTP/1-like headers from the HTTP/2 trailer data once appended a string like : to the target buffer, while this was recently changed to : (a space was added after the colon) but the following math wasn't updated correspondingly. When accessed, the data is read out of bounds and causes either a crash or that the (too large) data gets passed to client write. This could lead to a denial-of-service situation or an information disclosure if someone has a service that echoes back or uses the trailers for something.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
47(Track)
EG Risk 47/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
Severity91% × 45%
Exploitation5% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
5%
EPSS %ILE
91%
KEV
Not listed

Published

January 24, 2018

Last Modified

November 21, 2024

Advisory Details (5)

Auto-updated Jul 20, 2026
Patch available. Sources: redhat, github_pr.
github_pr

http2.c: fix incorrect trailer buffer size

Upstream fix in progress (PR #2231 · curl/curl, state=closed)

https://github.com/curl/curl/pull/2231
generic

curl - HTTP/2 trailer out-of-bounds read - CVE-2018-1000005

https://curl.haxx.se/docs/adv_2018-824a.html
redhat Patch Available
https://access.redhat.com/errata/RHSA-2019:1543
generic
http://www.securitytracker.com/id/1040273
generic

[SECURITY] [DSA 4098-1] curl security update

https://www.debian.org/security/2018/dsa-4098

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibcurl4-openssl-dev (7.47.0-1ubuntu2.6) @ xenial2026-05-28ubuntu
redhatjbcs-httpd24-curl2019-06-18redhat

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

(8 across 8 ecosystems)
Alpine:v3.4(1)
PackageVulnerable rangeFixed inDependents
curl7.19.2-r0 ... 7.57.0-r0 (73 versions)7.58.0-r0—
Alpine:v3.5(1)
PackageVulnerable rangeFixed inDependents
curl7.19.2-r0 ... 7.57.0-r0 (78 versions)7.58.0-r0—
Alpine:v3.6(1)
PackageVulnerable rangeFixed inDependents
curl7.19.2-r0 ... 7.57.0-r0 (82 versions)7.58.0-r0—
Alpine:v3.7(1)
PackageVulnerable rangeFixed inDependents
curl7.19.2-r0 ... 7.57.0-r0 (85 versions)7.58.0-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
curl—7.58.0-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
curl—7.58.0-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
curl—7.58.0-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
curl—7.58.0-1—

Weakness Classification(1)

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

All Vendor Advisories

(2)

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 6× in last 7d / 22× 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 135 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2018-1000005?
CVE-2018-1000005 is a critical vulnerability published on January 24, 2018. libcurl 7.49.0 to and including 7.57.0 contains an out bounds read in code handling HTTP/2 trailers. It was reported (https://github.com/curl/curl/pull/2231) that reading an HTTP/2 trailer could mess up future trailers since the stored size was one byte less than required. The problem is that the…
When was CVE-2018-1000005 disclosed?
CVE-2018-1000005 was first published in the National Vulnerability Database on January 24, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-1000005 actively exploited?
CVE-2018-1000005 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5% probability of exploitation in the next 30 days, which ranks it in the top 9.0% of all scored CVEs.
What is the CVSS score of CVE-2018-1000005?
CVE-2018-1000005 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2018-1000005?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-1000005, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-1000005

Explore →

Is Your Infrastructure Affected by CVE-2018-1000005?

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

Start Free Scan →Browse All CVEs