CVE-2026-80231: native CA store conn reuse
Published Sep 6, 2026
·Updated
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 (CURLSSLOPTNATIVECA) than when the connection was created.
Affected Software
4 affected componentsFixes available
redhat/libcurl
haxx curl>=7.71.0<8.22.0
debian/curl
7.88.1-10+deb12u157.88.1-10+deb12u58.14.1-2+deb13u58.14.1-2+deb13u78.23.0-28.24.0~rc1-1
IBM API Connect<=V10.0.8.0 - V10.0.8.13
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/curlto a version that resolves this vulnerability.Fixed in 7.88.1-10+deb12u15Fixed in 7.88.1-10+deb12u5Fixed in 8.14.1-2+deb13u5Fixed in 8.14.1-2+deb13u7Fixed in 8.23.0-2Fixed in 8.24.0~rc1-1
Event History
Sep 6, 2026
CVE Published
via MITRE·05:48 PM
Data Sourced
via MITRE·05:48 PM
DescriptionWeakness
Data Sourced
via Red Hat·06:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·06:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 8, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeakness
Nov 18, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Frequently Asked Questions
1
What application behavior should be reviewed to identify potential exposure?
Review HTTPS clients that may reuse existing connections to the same hostname while changing the CURLSSLOPT_NATIVE_CA setting between requests or transfers.
2
Is connection reuse part of the affected scenario?
Yes. The flaw involves reuse of an existing HTTPS connection that was established with a different Native CA Store setting.