CVE-2026-5545: wrong reuse of HTTP Negotiate connection

Published Apr 23, 2026
·
Updated

A flaw was found in libcurl. An application using libcurl that performs an authenticated HTTP(S) request after a Negotiate-authenticated one to the same host may incorrectly reuse the previous connection. This authentication bypass vulnerability allows the second request to be sent over a connection authenticated with different credentials, potentially leading to unauthorized access or information disclosure.

Other sources

libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) request after a Negotiate-authenticated one, when both use the same host.

— Launchpad

wrong reuse of HTTP Negotiate connection

— Microsoft

Affected Software

5 affected componentsFixes available
curl libcurl
haxx curl>=7.10.6<8.20.0
Microsoft azl3 curl 8.11.1-7<8.11.1-8
8.11.1-8
Microsoft azl3 cmake 3.30.3-13<3.30.3-14
3.30.3-14
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+deb13u48.20.0-58.21.0-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-8
  2. Upgrade

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

    Fixed in 3.30.3-14
  3. Upgrade

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

    Fixed in 8.14.1-2+deb13u4Fixed in 8.20.0-5Fixed in 8.21.0-2
  4. Configuration

    Avoid using HTTP Negotiate authentication in the application.

    libcurl HTTP Negotiate authentication = disabled

Event History

Apr 23, 2026
Data Sourced
via Red Hat·04:48 PM
DescriptionSeverityAffected Software
May 13, 2026
CVE Published
via MITRE·08:27 AM
Data Sourced
via MITRE·08:27 AM
DescriptionWeakness
Data Sourced
via NVD·01:01 PM
RemedyDescriptionSeverityWeaknessAffected Software
May 14, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-5545?

CVE-2026-5545 has a medium severity rating due to potential unauthorized access risks.

2

How do I fix CVE-2026-5545?

To fix CVE-2026-5545, upgrade to the latest version of libcurl that addresses this vulnerability.

3

What software is affected by CVE-2026-5545?

CVE-2026-5545 affects certain versions of curl and libcurl between 7.10.6 and 8.20.0.

4

What is the impact of CVE-2026-5545?

The impact of CVE-2026-5545 can lead to inadvertent reuse of connections, possibly resulting in authentication errors.

5

How can I determine if I am using a vulnerable version regarding CVE-2026-5545?

To determine if you are using a vulnerable version for CVE-2026-5545, check your libcurl version against the specified affected version range.

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