CVE-2026-80230

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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.

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: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

When CURLOPT_PINNEDPUBLICKEY is configured alongside options that disable standard peer verification (CURLOPT_SSL_VERIFYPEER = 0 and CURLOPT_SSL_VERIFYHOST = 0), libcurl fails to enforce public key pinning on connections established without a presented server certificate. Bypassing the pinning check under these disabled-verification conditions allows unauthenticated connections to succeed when they should be rejected.

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

Published

September 6, 2026

Last Modified

September 15, 2026

Advisory Details (3)

Auto-updated Sep 8, 2026
No patch confirmed yet.
generic

HackerOne

https://hackerone.com/reports/3969300
generic
https://curl.se/docs/CVE-2026-80230.json
generic

curl - OpenSSL pinning bypass - CVE-2026-80230

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

Vendor Advisories for CVE-2026-80230(2)

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

Affected Packages

(5 across 5 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
curl—8.22.0-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
curl—8.22.0-r0—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
curl7.88.1-10 ... 8.9.1-2~bpo12+1 (179 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
curl8.14.1-2 ... 8.22.0~rc3-1+exp1 (79 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
curl8.14.1-2 ... 8.22.0~rc3-1+exp1 (73 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 43× in last 7d / 75× 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-09-20 20:16 UTCEPSS rescore
  2. 2026-09-20 17:15 UTCVendor advisory
  3. 2026-09-20 17:15 UTCGHSA enrichment
  4. 2026-09-20 04:14 UTCEG score recompute
  5. 2026-09-20 04:14 UTCVendor advisory
  6. 2026-09-20 04:14 UTCGHSA enrichment
  7. 2026-09-19 15:18 UTCVendor advisory
  8. 2026-09-19 15:18 UTCGHSA enrichment
  9. 2026-09-19 02:23 UTCEG score recompute
  10. 2026-09-19 02:23 UTCVendor advisory
  11. 2026-09-19 02:23 UTCGHSA enrichment
  12. 2026-09-18 19:28 UTCEPSS rescore
  13. 2026-09-18 13:28 UTCVendor advisory
  14. 2026-09-18 13:28 UTCGHSA enrichment
  15. 2026-09-18 00:33 UTCEG score recompute
  16. 2026-09-18 00:33 UTCVendor advisory
  17. 2026-09-18 00:33 UTCGHSA enrichment
  18. 2026-09-17 11:38 UTCVendor advisory
  19. 2026-09-17 11:38 UTCGHSA enrichment
  20. 2026-09-16 22:42 UTCEG score recompute
  21. 2026-09-16 22:42 UTCVendor advisory
  22. 2026-09-16 22:42 UTCGHSA enrichment
  23. 2026-09-16 14:08 UTCEPSS rescore
  24. 2026-09-16 09:47 UTCEG score recompute
  25. 2026-09-16 09:47 UTCVendor advisory
Show 50 more
  1. 2026-09-16 09:47 UTCGHSA enrichment
  2. 2026-09-16 05:15 UTCEPSS rescore
  3. 2026-09-15 20:51 UTCVendor advisory
  4. 2026-09-15 20:51 UTCGHSA enrichment
  5. 2026-09-15 07:28 UTCVendor advisory
  6. 2026-09-15 07:28 UTCGHSA enrichment
  7. 2026-09-15 06:39 UTCEG score recompute
  8. 2026-09-15 06:39 UTCVendor advisory
  9. 2026-09-15 06:39 UTCGHSA enrichment
  10. 2026-09-15 03:12 UTCEPSS rescore
  11. 2026-09-15 03:12 UTCEPSS rescore
  12. 2026-09-15 01:46 UTCVendor advisory
  13. 2026-09-15 01:46 UTCGHSA enrichment
  14. 2026-09-14 12:51 UTCVendor advisory
  15. 2026-09-14 12:51 UTCGHSA enrichment
  16. 2026-09-13 23:56 UTCEG score recompute
  17. 2026-09-13 23:56 UTCVendor advisory
  18. 2026-09-13 23:56 UTCGHSA enrichment
  19. 2026-09-13 11:01 UTCVendor advisory
  20. 2026-09-13 11:01 UTCGHSA enrichment
  21. 2026-09-12 22:06 UTCEG score recompute
  22. 2026-09-12 22:06 UTCVendor advisory
  23. 2026-09-12 22:06 UTCGHSA enrichment
  24. 2026-09-12 09:11 UTCVendor advisory
  25. 2026-09-12 09:11 UTCGHSA enrichment
  26. 2026-09-11 20:16 UTCEG score recompute
  27. 2026-09-11 20:16 UTCVendor advisory
  28. 2026-09-11 20:16 UTCGHSA enrichment
  29. 2026-09-11 14:53 UTCEPSS rescore
  30. 2026-09-11 14:53 UTCEPSS rescore
  31. 2026-09-11 14:04 UTCEG score recompute
  32. 2026-09-11 14:04 UTCGHSA enrichment
  33. 2026-09-11 01:09 UTCGHSA enrichment
  34. 2026-09-10 12:14 UTCEG score recompute
  35. 2026-09-10 12:14 UTCGHSA enrichment
  36. 2026-09-09 23:19 UTCGHSA enrichment
  37. 2026-09-09 08:49 UTCEG score recompute
  38. 2026-09-09 08:49 UTCVendor advisory
  39. 2026-09-09 08:49 UTCGHSA enrichment
  40. 2026-09-08 22:01 UTCEPSS rescore
  41. 2026-09-08 19:54 UTCEG score recompute
  42. 2026-09-08 19:54 UTCGHSA enrichment
  43. 2026-09-08 19:02 UTCEG score recompute▲ 7.50
  44. 2026-09-08 19:02 UTCGHSA enrichment
  45. 2026-09-08 18:59 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  46. 2026-09-08 15:00 UTCEG score recompute
  47. 2026-09-08 15:00 UTCGHSA enrichment
  48. 2026-09-06 18:20 UTCNVD update
  49. 2026-09-06 17:59 UTCEG score recompute
  50. 2026-09-06 17:58 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-80230?
CVE-2026-80230 is a high vulnerability published on September 6, 2026. When CURLOPT_PINNEDPUBLICKEY is configured alongside options that disable standard peer verification (CURLOPTSSLVERIFYPEER = 0 and CURLOPTSSLVERIFYHOST = 0), libcurl fails to enforce public key pinning on connections established without a presented server certificate. Bypassing the pinning check…
When was CVE-2026-80230 disclosed?
CVE-2026-80230 was first published in the National Vulnerability Database on September 6, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80230 actively exploited?
CVE-2026-80230 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.3% of all scored CVEs.
What is the CVSS score of CVE-2026-80230?
CVE-2026-80230 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-80230?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80230, 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-80230

Explore →

Is Your Infrastructure Affected by CVE-2026-80230?

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

Start Free Scan →Browse All CVEs