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.
Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Sun, 06 Sep 2026 19:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-295 |
Sun, 06 Sep 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | OpenSSL pinning bypass | |
| References |
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: curl
Published:
Updated: 2026-09-06T17:48:16.262Z
Reserved: 2026-08-26T04:24:25.568Z
Link: CVE-2026-80230
No data.
Status : Received
Published: 2026-09-06T18:17:22.327
Modified: 2026-09-06T18:17:22.327
Link: CVE-2026-80230
No data.
OpenCVE Enrichment
Updated: 2026-09-06T19:30:11Z