CVE-2026-8932

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-03. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

libcurl would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse.

libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. However, some TLS settings related to client certificates were left out from the configuration match checks, making them match too easily. In particular options related to the private key.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 7, 2026

Advisory Details (3)

Auto-updated Jul 7, 2026
No patch confirmed yet.
generic

HackerOne

https://hackerone.com/reports/3733910
generic
https://curl.se/docs/CVE-2026-8932.json
generic

curl - incomplete mTLS config matching in conn reuse - CVE-2026-8932

https://curl.se/docs/CVE-2026-8932.html

Vendor Advisories for CVE-2026-8932(4)

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 / EcosystemFixed in / PatchReleasedSource
redhatrust-main-1.96.1-1.hum12026-07-02redhat
redhatcurl-main-8.21.0-0.1.hum12026-06-24redhat

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

(5 across 5 ecosystems)
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
curl—8.21.0-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
curl7.74.0-1.3 ... 8.9.1-2~bpo12+1 (219 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
curl7.88.1-10 ... 8.9.1-2~bpo12+1 (174 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
curl8.14.1-2 ... 8.21.0~rc3-1+exp1 (74 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
curl8.14.1-2 ... 8.21.0~rc1-1+exp1 (59 versions)8.21.0~rc2-1—

Data Freshness Timeline

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

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-8932?
CVE-2026-8932 is a high vulnerability published on July 3, 2026. libcurl would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse. libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. However, some TLS…
When was CVE-2026-8932 disclosed?
CVE-2026-8932 was first published in the National Vulnerability Database on July 3, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-8932 actively exploited?
CVE-2026-8932 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 66.9% of all scored CVEs.
What is the CVSS score of CVE-2026-8932?
CVE-2026-8932 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-8932?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8932, 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-2026-8932

Explore →

Is Your Infrastructure Affected by CVE-2026-8932?

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

Start Free Scan →Browse All CVEs