A flaw in libcurl makes it wrongly reuse an existing HTTPS connection setup
for a given hostname even when using a different Native CA Store setting
(CURLSSLOPT_NATIVE_CA) than when the connection was created.
CVE-2026-80231
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-06. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- 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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 1%
- EPSS %ILE
- 59%
- KEV
- Not listed
Published
September 6, 2026
Last Modified
September 15, 2026
Advisory Details (3)
Auto-updated Sep 8, 2026Vendor Advisories for CVE-2026-80231(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 2 ecosystems)
Alpine:v3.23(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | — | 8.22.0-r0 | — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | — | 8.22.0-r0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 42× in last 7d / 67× 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.
- 2026-09-19 02:58 UTCEG score recompute
- 2026-09-19 02:58 UTCVendor advisory
- 2026-09-19 02:58 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 13:57 UTCVendor advisory
- 2026-09-18 13:57 UTCGHSA enrichment
- 2026-09-18 00:54 UTCEG score recompute
- 2026-09-18 00:54 UTCVendor advisory
- 2026-09-18 00:54 UTCGHSA enrichment
- 2026-09-17 11:54 UTCVendor advisory
- 2026-09-17 11:54 UTCGHSA enrichment
- 2026-09-16 22:53 UTCEG score recompute
- 2026-09-16 22:53 UTCVendor advisory
- 2026-09-16 22:53 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 09:52 UTCEG score recompute
- 2026-09-16 09:52 UTCVendor advisory
- 2026-09-16 09:52 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 20:51 UTCVendor advisory
- 2026-09-15 20:51 UTCGHSA enrichment
- 2026-09-15 07:28 UTCVendor advisory
- 2026-09-15 07:28 UTCGHSA enrichment
- 2026-09-15 06:39 UTCEG score recompute
- 2026-09-15 06:39 UTCVendor advisory
Show 42 moreShow fewer
- 2026-09-15 06:39 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 02:20 UTCVendor advisory
- 2026-09-15 02:20 UTCGHSA enrichment
- 2026-09-14 13:18 UTCVendor advisory
- 2026-09-14 13:18 UTCGHSA enrichment
- 2026-09-14 00:17 UTCEG score recompute
- 2026-09-14 00:17 UTCVendor advisory
- 2026-09-14 00:17 UTCGHSA enrichment
- 2026-09-13 11:17 UTCVendor advisory
- 2026-09-13 11:17 UTCGHSA enrichment
- 2026-09-12 22:17 UTCEG score recompute
- 2026-09-12 22:17 UTCVendor advisory
- 2026-09-12 22:17 UTCGHSA enrichment
- 2026-09-12 09:16 UTCVendor advisory
- 2026-09-12 09:16 UTCGHSA enrichment
- 2026-09-11 20:16 UTCEG score recompute
- 2026-09-11 20:16 UTCVendor advisory
- 2026-09-11 20:16 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:21 UTCEG score recompute
- 2026-09-11 14:21 UTCGHSA enrichment
- 2026-09-11 01:20 UTCGHSA enrichment
- 2026-09-10 12:20 UTCEG score recompute
- 2026-09-10 12:19 UTCGHSA enrichment
- 2026-09-09 23:19 UTCGHSA enrichment
- 2026-09-09 08:55 UTCEG score recompute
- 2026-09-09 08:55 UTCVendor advisory
- 2026-09-09 08:55 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 19:54 UTCEG score recompute
- 2026-09-08 19:54 UTCGHSA enrichment
- 2026-09-08 19:02 UTCEG score recompute▲ 7.50
- 2026-09-08 19:02 UTCGHSA enrichment
- 2026-09-08 18:59 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
- 2026-09-08 15:00 UTCEG score recompute
- 2026-09-08 15:00 UTCGHSA enrichment
- 2026-09-06 18:20 UTCNVD update
- 2026-09-06 17:59 UTCEG score recompute
- 2026-09-06 17:58 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-80231?
When was CVE-2026-80231 disclosed?
Is CVE-2026-80231 actively exploited?
What is the CVSS score of CVE-2026-80231?
How do I remediate CVE-2026-80231?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-80231
Is Your Infrastructure Affected by CVE-2026-80231?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.