Summary
This update for curl fixes the following issues
- CVE-2026-4873: connection reuse ignores TLS requirement (bsc#1262631).
- 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).
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| SUSE · SLES 12 SP5 Linux Enterprise Server LTSS Extended Security 12 SP5 | curl | 8.0.1-11.123.1 |
Vulnerabilities 6
-
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
connection reuse ignores TLS requirement
A vulnerability exists where a connection requiring TLS incorrectly reuses an existing unencrypted connection from the same connection pool. If an initial transfer is made in clear-text (via IMAP, SMTP, or POP3), a subsequent request to that same host bypasse…
-
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.
References
-
report
https://bugzilla.suse.com/1262631
-
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
-
web
https://www.suse.com/security/cve/CVE-2026-4873
-
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