Skip to content
OpenAdvisories
Critical SUSE-SU-2026:3798-1 7 CVEs

Security update for curl

Published Aug 25, 2026 · Updated Aug 27, 2026

Summary

This update for curl fixes the following issues:

- CVE-2026-5545: wrong reuse of HTTP Negotiate connection (bsc#1262632).
- CVE-2026-5773: wrong reuse of SMB connection (bsc#1262633).
- CVE-2026-6253: proxy credentials leak over redirect-to proxy (bsc#1262635).
- CVE-2026-6276: stale custom cookie host causes cookie leak (bsc#1262636).
- CVE-2026-6429: netrc credential leak with reused proxy connection (bsc#1262638).
- CVE-2026-7168: cross-proxy Digest auth state leak (bsc#1263440).
- CVE-2026-8926: password leak with netrc and user in URL (bsc#1268412).

Fixed packages 1

ReleasePackageFixed in
SUSE · SLES 15 SP7 Linux Enterprise Module for Basesystem 15 SP7 curl 8.14.1-150700.7.23.1

Vulnerabilities 7

  • Critical 9.1

    password leak with netrc and user in URL

    When asking curl to use a `.netrc` file to find credentials and at the same time specifying a URL with a username (without a password), like `https://user@example.com/`, curl could wrongly get and use the password for *another* user set in the `.netrc` file f…

  • High 7.5

    wrong reuse of SMB connection

    libcurl might in some circumstances reuse the wrong connection for SMB(S) transfers. libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead. When reusing a connection a range of criteria mu…

  • High 7.5

    stale custom cookie host causes cookie leak

    Using libcurl, when a custom `Host:` header is first set for an HTTP request and a second request is subsequently done using the same *easy handle* but without the custom `Host:` header set, the second request would use stale information and pass on cookies m…

  • Medium 6.5

    wrong reuse of HTTP Negotiate connection

    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. libcurl features a pool of recent connections so that subsequent requests can re…

  • Medium 5.9

    proxy credentials leak over redirect-to proxy

    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 se…

  • Medium 5.3

    netrc credential leak with reused proxy connection

    When asked to both use a `.netrc` file for credentials and to follow HTTP redirects, libcurl could leak the password used for the first host to the followed-to host under certain circumstances.

  • Medium 5.3

    cross-proxy Digest auth state leak

    Successfully using libcurl to do a transfer over a specific HTTP proxy (`proxyA`) with **Digest** authentication and then changing the proxy host to a second one (`proxyB`) for a second transfer, reusing the same handle, makes libcurl wrongly pass on the `Pro…

References

  • report
    https://bugzilla.suse.com/1262632
  • report
    https://bugzilla.suse.com/1262633
  • report
    https://bugzilla.suse.com/1262635
  • report
    https://bugzilla.suse.com/1262636
  • report
    https://bugzilla.suse.com/1262638
  • report
    https://bugzilla.suse.com/1263440
  • report
    https://bugzilla.suse.com/1268412
  • web
    https://www.suse.com/security/cve/CVE-2026-5545
  • web
    https://www.suse.com/security/cve/CVE-2026-5773
  • web
    https://www.suse.com/security/cve/CVE-2026-6253
  • web
    https://www.suse.com/security/cve/CVE-2026-6276
  • web
    https://www.suse.com/security/cve/CVE-2026-6429
  • web
    https://www.suse.com/security/cve/CVE-2026-7168
  • web
    https://www.suse.com/security/cve/CVE-2026-8926