CVE-2026-8932: incomplete mTLS config matching in conn reuse

Published Jul 3, 2026
·
Updated

incomplete mTLS config matching in conn reuse

Other sources

libcurl would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse.

Launchpad

Affected Software

4 affected componentsFixes available
libcurl
haxx curl>=7.7<8.21.0
Microsoft azl3 curl 8.11.1-9<8.11.1-10
8.11.1-10
debian/curl<=7.74.0-1.3+deb11u13, <=7.74.0-1.3+deb11u16, <=7.88.1-10+deb12u15, <=7.88.1-10+deb12u5, <=8.14.1-2+deb13u4
8.21.0-28.22.0~rc2-2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.11.1-10
  2. Upgrade

    Upgrade debian/curl to a version that resolves this vulnerability.

    Fixed in 8.21.0-2Fixed in 8.22.0~rc2-2

Event History

Jul 3, 2026
CVE Published
via MITRE·06:16 AM
Data Sourced
via MITRE·06:16 AM
DescriptionWeakness
Data Sourced
via Red Hat·07:01 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·07:16 AM
RemedyDescriptionSeverityAffected Software
Jul 4, 2026
Data Sourced
via Microsoft·08:04 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:04 AM
DescriptionSeverity
Aug 24, 2026
Data Sourced
via Debian·08:07 PM
DescriptionAffected Software
Data Sourced
via Launchpad·08:07 PM
Description
Aug 25, 2026
Data Sourced
via Ubuntu·08:06 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-8932?

CVE-2026-8932 has a risk rating of 21, indicating a significant security concern.

2

How does CVE-2026-8932 affect libcurl's connection management?

CVE-2026-8932 allows libcurl to reuse a connection even when mTLS configuration changes occur that should have prevented the reuse.

3

What are the potential risks of exploiting CVE-2026-8932?

Exploiting CVE-2026-8932 could lead to unauthorized access or data leakage due to improper mTLS connection handling.

4

How can I fix CVE-2026-8932 in my application?

To fix CVE-2026-8932, you should update libcurl to the latest version where the issue has been resolved.

5

When was CVE-2026-8932 published?

CVE-2026-8932 was published on July 3, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203