UBUNTU-CVE-2026-86414: Low severity ubuntu/curl vulnerability

Published Oct 14, 2026
·
Updated

An HTTP proxy can trick libcurl into sending the origin's credentials (Basic password, or a Negotiate/Kerberos ticket) to the proxy itself, by answering the CONNECT tunnel request with 401 WWW-Authenticate: instead of the expected 407 Proxy-Authenticate:.

Affected Software

8 affected componentsFixes available
ubuntu/curl<7.35.0-1ubuntu2.20+esm24
7.35.0-1ubuntu2.20+esm24
ubuntu/curl<7.47.0-1ubuntu2.19+esm21
7.47.0-1ubuntu2.19+esm21
ubuntu/curl<7.58.0-2ubuntu3.24+esm15
7.58.0-2ubuntu3.24+esm15
ubuntu/curl<7.68.0-1ubuntu2.25+esm10
7.68.0-1ubuntu2.25+esm10
ubuntu/curl<7.81.0-1ubuntu1.30
7.81.0-1ubuntu1.30
ubuntu/curl<8.5.0-2ubuntu10.16
8.5.0-2ubuntu10.16
ubuntu/curl<8.20.0-2ubuntu11.1
8.20.0-2ubuntu11.1
ubuntu/curl<8.18.0-1ubuntu2.8
8.18.0-1ubuntu2.8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 7.35.0-1ubuntu2.20+esm24
  2. Upgrade

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

    Fixed in 7.47.0-1ubuntu2.19+esm21
  3. Upgrade

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

    Fixed in 7.58.0-2ubuntu3.24+esm15
  4. Upgrade

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

    Fixed in 7.68.0-1ubuntu2.25+esm10
  5. Upgrade

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

    Fixed in 7.81.0-1ubuntu1.30
  6. Upgrade

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

    Fixed in 8.5.0-2ubuntu10.16
  7. Upgrade

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

    Fixed in 8.20.0-2ubuntu11.1
  8. Upgrade

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

    Fixed in 8.18.0-1ubuntu2.8

Event History

Oct 14, 2026
CVE Published
via OSV·06:00 AM
Data Sourced
via OSV·06:00 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What does an attacker need to exploit this issue?

An attacker needs to control or operate an HTTP proxy used by the affected libcurl client. The proxy must respond to a CONNECT tunnel request with a 401 response containing WWW-Authenticate rather than the expected 407 Proxy-Authenticate response.

2

Which credentials could be disclosed to the proxy?

The proxy may receive the origin server's Basic authentication password or a Negotiate/Kerberos ticket. The issue concerns credentials that libcurl should send to the origin, not the proxy.

3

Are clients that do not use an HTTP proxy exposed?

The described attack depends on an HTTP proxy handling a CONNECT tunnel request. Clients not using such a proxy are not exposed through this attack path.

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