CVE-2026-8286

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

A vulnerability exists where a new transfer that uses STARTTLS to upgrade the connection might reuse an existing live connection even though the TLS configuration mismatches so it should not.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
52(Track*)
EG Risk 52/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
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 7, 2026

Advisory Details (3)

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

HackerOne

https://hackerone.com/reports/3718195
generic
https://curl.se/docs/CVE-2026-8286.json
generic

curl - wrong STARTTLS connection reuse - CVE-2026-8286

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

Vendor Advisories for CVE-2026-8286(8)

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibcurl4-openssl-dev (7.68.0-1ubuntu2.25+esm4) @ focal2026-08-25ubuntu
redhatrhui5/rhua-tp-rhel9:17872412602026-08-24redhat
redhatcurl-0:7.61.1-34.el8_10.132026-08-20redhat
redhatcurl-0:7.76.1-40.el9_8.52026-08-17redhat
redhatcurl-0:8.12.1-4.el10_2.32026-08-17redhat
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—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 37× in last 7d / 163× 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 229 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-8286?
CVE-2026-8286 is a high vulnerability published on July 3, 2026. A vulnerability exists where a new transfer that uses STARTTLS to upgrade the connection might reuse an existing live connection even though the TLS configuration mismatches so it should not.
When was CVE-2026-8286 disclosed?
CVE-2026-8286 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-8286 actively exploited?
CVE-2026-8286 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 76.9% of all scored CVEs.
What is the CVSS score of CVE-2026-8286?
CVE-2026-8286 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-8286?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8286, 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-8286

Explore →

Is Your Infrastructure Affected by CVE-2026-8286?

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

Start Free Scan →Browse All CVEs