CVE-2026-6253: proxy credentials leak over redirect-to proxy

Published Apr 23, 2026
·
Updated

A flaw was found in curl. When curl is configured to use specific proxies for different URL schemes, and a redirect occurs from a URL using a credentialed proxy to a URL using a non-credentialed proxy, curl may inadvertently send the credentials of the first proxy to the second. This can lead to the unauthorized disclosure of proxy credentials (CWE-522), potentially allowing an attacker to gain unauthorized access or information.

Other sources

curl might erroneously pass on credentials for a first proxy to a second proxy.

This can happen when the following conditions are true:

1. curl is setup to use specific different proxies for different URL schemes 2. the first proxy needs credentials 3. the second proxy uses no credentials 4. while using the first proxy (using say http://), curl is asked to follow a redirect to a URL using another scheme (say https://), accessed using a second, different, proxy

— MITRE

proxy credentials leak over redirect-to proxy

— Microsoft

Affected Software

4 affected componentsFixes available
curl curl
haxx curl>=7.14.1<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

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 3.30.3-14
  2. Upgrade

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

    Fixed in 8.11.1-8

Event History

Apr 23, 2026
Data Sourced
via Red Hat·04:48 PM
DescriptionSeverityAffected Software
May 13, 2026
CVE Published
via MITRE·08:28 AM
Data Sourced
via MITRE·08:28 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-6253?

CVE-2026-6253 is classified as a medium severity vulnerability due to the potential credential leakage.

2

How do I fix CVE-2026-6253?

To fix CVE-2026-6253, ensure that you are using the latest version of curl where this vulnerability has been addressed.

3

What versions of curl are affected by CVE-2026-6253?

CVE-2026-6253 affects curl versions between 7.14.1 and 8.20.0 inclusive.

4

What is the main risk associated with CVE-2026-6253?

The main risk associated with CVE-2026-6253 is the unintended leak of proxy credentials during redirection between proxies.

5

How can I mitigate the risks of CVE-2026-6253?

To mitigate the risks of CVE-2026-6253, avoid configuring multiple proxies with differing authentication requirements for the same session.

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