What is CVE-2026-80230?
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.
1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 29 days ago.
Severity and exploitation probability
- EPSS (FIRST)
- 0.1% probability of exploitation in the next 30 days, higher than 3.8% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 0.2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-09-06
Is CVE-2026-80230 being exploited?
It currently carries a trending score of 31 in the Threadlinqs vulnerability feed.
Affected products and versions
- curl: curl
How to fix CVE-2026-80230
No vendor patch reference has been recorded for CVE-2026-80230 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-80230
No threat campaign in the Threadlinqs corpus currently references CVE-2026-80230, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.
Sources
Enriched from CVE.org, GitHub Security Advisories, NVD, FIRST EPSS. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.