cve.bz

CVE-2026-80230 haxx curl: Improper Certificate Validation

7.5 highExploit referenceEPSS 0.4%Fix available

High (7.5) in haxx curl. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-09-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-80230 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-80230?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-80230?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-80230 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
curlfrom 7.45.0 before 8.14.2
curlfrom 8.15.0 before 8.16.1
curlfrom 8.17.0 before 8.20.1
curlfrom 8.21.0 before 8.22.0
curl8.21.0
curl8.20.0
curl8.19.0
curl8.18.0
curl8.17.0
curl8.16.0
curl8.15.0
curl8.14.1
curl8.14.0
curl8.13.0
curl8.12.1
curl8.12.0
curl8.11.1
curl8.11.0
curl8.10.1
curl8.10.0
curl8.9.1
curl8.9.0
curl8.8.0
curl8.7.1
curl8.7.0
curl8.6.0
curl8.5.0
curl8.4.0
curl8.3.0
curl8.2.1
curl8.2.0
curl8.1.2
curl8.1.1
curl8.1.0
curl8.0.1
curl8.0.0
curl7.88.1
curl7.88.0
curl7.87.0
curl7.86.0
curl7.85.0
curl7.84.0
curl7.83.1
curl7.83.0
curl7.82.0
curl7.81.0
curl7.80.0
curl7.79.1
curl7.79.0
curl7.78.0
curl7.77.0
curl7.76.1
curl7.76.0
curl7.75.0
curl7.74.0
curl7.73.0
curl7.72.0
curl7.71.1
curl7.71.0
curl7.70.0
curl7.69.1
curl7.69.0
curl7.68.0
curl7.67.0
curl7.66.0
curl7.65.3
curl7.65.2
curl7.65.1
curl7.65.0
curl7.64.1
curl7.64.0
curl7.63.0
curl7.62.0
curl7.61.1
curl7.61.0
curl7.60.0
curl7.59.0
curl7.58.0
curl7.57.0
curl7.56.1
curl7.56.0
curl7.55.1
curl7.55.0
curl7.54.1
curl7.54.0
curl7.53.1
curl7.53.0
curl7.52.1
curl7.52.0
curl7.51.0
curl7.50.3
curl7.50.2
curl7.50.1
curl7.50.0
curl7.49.1
curl7.49.0
curl7.48.0
curl7.47.1
curl7.47.0
curl7.46.0
curl7.45.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13curlno fix listedDEBIAN-CVE-2026-80230
Debian14curl8.22.0~rc3-1DEBIAN-CVE-2026-80230
Ubuntu22.04:LTScurl7.81.0-1ubuntu1.29UBUNTU-CVE-2026-80230 USN-8820-1
Ubuntu24.04:LTScurl8.5.0-2ubuntu10.15UBUNTU-CVE-2026-80230 USN-8820-1
Ubuntu26.04:LTScurl8.18.0-1ubuntu2.7UBUNTU-CVE-2026-80230 USN-8820-1
Ubuntu26.10curl8.20.0-2ubuntu11UBUNTU-CVE-2026-80230
UbuntuPro:16.04:LTScurl7.47.0-1ubuntu2.19+esm20UBUNTU-CVE-2026-80230 USN-8820-1
UbuntuPro:18.04:LTScurl7.58.0-2ubuntu3.24+esm14UBUNTU-CVE-2026-80230 USN-8820-1
UbuntuPro:20.04:LTScurl7.68.0-1ubuntu2.25+esm9UBUNTU-CVE-2026-80230 USN-8820-1
Red Hathummingbird:1curl, libcurl, libcurl-devel and 1 more0:8.22.0-0.1.hum1RHSA-2026:63161
SUSELinux Enterprise Micro 5.3, Linux Enterprise Micro 5.4, Linux Enterprise Micro 5.5curl8.14.1-150400.5.91.1SUSE-SU-2026:3958-1
SUSELinux Enterprise Module for Basesystem 15 SP7curl8.14.1-150700.7.26.1SUSE-SU-2026:4048-1
SUSELinux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6curl8.14.1-150600.4.51.1SUSE-SU-2026:4047-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0curl, curl-mini8.14.1-160000.9.1SUSE-SU-2026:23638-1
SUSELinux Enterprise Server LTSS Extended Security 12 SP5curl8.0.1-11.129.1SUSE-SU-2026:4071-1
SUSELinux Micro 6.1curl8.14.1-slfo.1.1_10.1SUSE-SU-2026:23521-1
SUSELinux Micro 6.2curl8.14.1-160000.9.1SUSE-SU-2026:23498-1
openSUSELeap 16.0curl8.14.1-160000.9.1openSUSE-SU-2026:21774-1
openSUSETumbleweedcurl8.22.0-1.1openSUSE-SU-2026:11696-1
Alpinev3.23, v3.24curl8.22.0-r0ALPINE-CVE-2026-80230
Azure Linux3curl8.11.1-12AZL-99770
Azure Linux3mysqlno fix listedAZL-99789
Azure Linux3rustno fix listedAZL-99816 AZL-99846
Azure Linux3tensorflowno fix listedAZL-99873
Alpaquita23, 25, streamcurl8.22.0-r0BELL-CVE-2026-80230
BellSoft Hardened Containersstreamcurl8.22.0-r0BELL-CVE-2026-80230

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpine · Alpaquita · BellSoft Hardened Containers.

Red Hat

Red Hat rates this Low.

Red Hat's statement

This Low impact flaw in curl arises when public key pinning is enabled alongside explicitly disabled SSL/TLS peer verification. In such an atypical and insecure configuration, libcurl fails to enforce the public key pinning, allowing unauthenticated connections to proceed without proper certificate validation. Red Hat products typically employ secure default configurations that enable full peer verification, thus reducing exposure to this issue.

Red Hat's mitigation

To mitigate this issue, ensure that SSL/TLS peer verification is enabled by setting `CURLOPT_SSL_VERIFYPEER` and `CURLOPT_SSL_VERIFYHOST` to `1` (or not explicitly disabling them). This ensures that libcurl properly enforces public key pinning and validates server certificates.

ProductPackageStateAdvisory
Red Hat Hardened Imagescurl-main-8.22.0-0.1.hum1Fixed 2026-09-03RHSA-2026:63161
Confidential Compute Attestationbuild-of-trustee/trustee-rhel9Not affected
Confidential Compute Attestationopenshift-sandboxed-containers/osc-podvm-payload-rhel9Not affected
Red Hat Enterprise Linux 10curlAffected
Red Hat Enterprise Linux 10igvmNot affected
Red Hat Enterprise Linux 10rustNot affected
Red Hat Enterprise Linux 10s390utilsNot affected
Red Hat Enterprise Linux 10snphostNot affected
Red Hat Enterprise Linux 10trusteeNot affected
Red Hat Enterprise Linux 6curlNot affected
Red Hat Enterprise Linux 7curlNot affected
Red Hat Enterprise Linux 8curlFix deferred
Red Hat Enterprise Linux 9curlAffected
Red Hat Enterprise Linux 9rustNot affected
Red Hat Enterprise Linux 9snphostNot affected
Red Hat Enterprise Linux AI (RHEL AI) 3rustNot affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-ai-gateway-operator-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-core-bff-rhel9Under investigation
Red Hat OpenShift AI (RHOAI)rhoai/odh-dashboard-operator-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-dashboard-rhel9Under investigation
35 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-80230.

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON