Описание
Security update for curl
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).
Список пакетов
Container bci/bci-sle15-kernel-module-devel:latest
Container bci/golang:1.25
Container bci/golang:1.25-openssl
Container bci/golang:1.26
Container bci/golang:latest
Container bci/node:22
Container bci/openjdk:17
Container bci/openjdk:21
Container bci/openjdk:latest
Container bci/php-apache:latest
Container bci/php-fpm:latest
Container bci/php:latest
Container bci/python:3
Container bci/python:latest
Container bci/ruby:2
Container bci/ruby:latest
Container bci/rust:1.96
Container bci/rust:latest
Container bci/spack:latest
Container private-registry/1.2/harbor-trivy-adapter:latest
Container private-registry/harbor-trivy-adapter:latest
Container suse/kea:2.6
Container suse/kiosk/firefox-esr:latest
Container suse/postgres:16
Container suse/postgres:16.14
Container suse/postgres:17
Container suse/postgres:17.10
Container suse/postgres:latest
Container suse/sle15:latest
Image SLES15-SP7-SAP-GCE-3P
SUSE Linux Enterprise Module for Basesystem 15 SP7
Ссылки
- Link for SUSE-SU-2026:3798-1
- E-Mail link for SUSE-SU-2026:3798-1
- SUSE Security Ratings
- SUSE Bug 1262632
- SUSE Bug 1262633
- SUSE Bug 1262635
- SUSE Bug 1262636
- SUSE Bug 1262638
- SUSE Bug 1263440
- SUSE Bug 1268412
- SUSE CVE CVE-2026-5545 page
- SUSE CVE CVE-2026-5773 page
- SUSE CVE CVE-2026-6253 page
- SUSE CVE CVE-2026-6276 page
- SUSE CVE CVE-2026-6429 page
- SUSE CVE CVE-2026-7168 page
- SUSE CVE CVE-2026-8926 page
Описание
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 reuse an existing connection to avoid overhead. When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different credentials. An application that first uses Negotiate authentication to a server with `user1:password1` and then does another operation to the same server asking for any authentication method but for `user2:password2` (while the previous connection is still alive) - the second request gets confused and wrongly reuses the same connection and sends the new request over that connection thinking it uses a mix of user1's and user2's credentials when it is in fact still using the connection authenticated for user1...
Затронутые продукты
Ссылки
- CVE-2026-5545
- SUSE Bug 1262632
- SUSE Bug 1268407
Описание
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 must be met. Due to a logical error in the code, a network transfer operation that was requested by an application could wrongfully reuse an existing SMB connection to the same server that was using a different 'share' than the new subsequent transfer should. This could in unlucky situations lead to the download of the wrong file or the upload of a file to the wrong place. When this happens, the same credentials are used and the server name is the same.
Затронутые продукты
Ссылки
- CVE-2026-5773
- SUSE Bug 1262633
Описание
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
Затронутые продукты
Ссылки
- CVE-2026-6253
- SUSE Bug 1262635
- SUSE Bug 1268299
Описание
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 meant for the first host in the second request. Leak them.
Затронутые продукты
Ссылки
- CVE-2026-6276
- SUSE Bug 1262636
Описание
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.
Затронутые продукты
Ссылки
- CVE-2026-6429
- SUSE Bug 1262638
Описание
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 `Proxy-Authorization:` header field meant for `proxyA`, to `proxyB`.
Затронутые продукты
Ссылки
- CVE-2026-7168
- SUSE Bug 1263440
- SUSE Bug 1268413
- SUSE Bug 1268426
Описание
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 for that host if such a one exists and there is no match for the specified user.
Затронутые продукты
Ссылки
- CVE-2026-8926
- SUSE Bug 1268412