Security update for curl SUSE Patch security@suse.de SUSE Security Team SUSE-SU-2026:0903-1 Final 1 1 2026-03-17T10:04:47Z current 2026-03-17T10:04:47Z 2026-03-17T10:04:47Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z Security update for curl This update for curl fixes the following issues: - CVE-2026-1965: bad reuse of HTTP Negotiate connection (bsc#1259362). - CVE-2026-3783: token leak with redirect and netrc (bsc#1259363). - CVE-2026-3784: wrong proxy connection reuse with credentials (bsc#1259364). - CVE-2026-3805: use after free in SMB connection reuse (bsc#1259365). The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). Container private-registry/harbor-trivy-adapter:latest-2026-903,Image pr_15_7-2026-903,SUSE-2026-903,SUSE-SLE-Module-Basesystem-15-SP7-2026-903 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/update/announcement/2026/suse-su-20260903-1/ Link for SUSE-SU-2026:0903-1 https://lists.suse.com/pipermail/sle-security-updates/2026-March/024702.html E-Mail link for SUSE-SU-2026:0903-1 https://www.suse.com/support/security/rating/ SUSE Security Ratings https://bugzilla.suse.com/1259362 SUSE Bug 1259362 https://bugzilla.suse.com/1259363 SUSE Bug 1259363 https://bugzilla.suse.com/1259364 SUSE Bug 1259364 https://bugzilla.suse.com/1259365 SUSE Bug 1259365 https://www.suse.com/security/cve/CVE-2026-1965/ SUSE CVE CVE-2026-1965 page https://www.suse.com/security/cve/CVE-2026-3783/ SUSE CVE CVE-2026-3783 page https://www.suse.com/security/cve/CVE-2026-3784/ SUSE CVE CVE-2026-3784 page https://www.suse.com/security/cve/CVE-2026-3805/ SUSE CVE CVE-2026-3805 page Container private-registry/harbor-trivy-adapter:latest Image pr_15_7 SUSE Linux Enterprise Module for Basesystem 15 SP7 libcurl4-8.14.1-150700.7.14.1 curl-8.14.1-150700.7.14.1 curl-fish-completion-8.14.1-150700.7.14.1 curl-zsh-completion-8.14.1-150700.7.14.1 libcurl-devel-8.14.1-150700.7.14.1 libcurl-devel-32bit-8.14.1-150700.7.14.1 libcurl-devel-64bit-8.14.1-150700.7.14.1 libcurl-devel-doc-8.14.1-150700.7.14.1 libcurl-mini4-8.14.1-150700.7.14.1 libcurl4-32bit-8.14.1-150700.7.14.1 libcurl4-64bit-8.14.1-150700.7.14.1 libcurl4-8.14.1-150700.7.14.1 as a component of Container private-registry/harbor-trivy-adapter:latest libcurl4-8.14.1-150700.7.14.1 as a component of Image pr_15_7 curl-8.14.1-150700.7.14.1 as a component of SUSE Linux Enterprise Module for Basesystem 15 SP7 libcurl-devel-8.14.1-150700.7.14.1 as a component of SUSE Linux Enterprise Module for Basesystem 15 SP7 libcurl4-8.14.1-150700.7.14.1 as a component of SUSE Linux Enterprise Module for Basesystem 15 SP7 libcurl4-32bit-8.14.1-150700.7.14.1 as a component of SUSE Linux Enterprise Module for Basesystem 15 SP7 libcurl can in some circumstances reuse the wrong connection when asked to do an Negotiate-authenticated HTTP or HTTPS request. 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 criterion must first 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. One underlying reason being that Negotiate sometimes authenticates *connections* and not *requests*, contrary to how HTTP is designed to work. An application that allows Negotiate authentication to a server (that responds wanting Negotiate) with `user1:password1` and then does another operation to the same server also using Negotiate but with `user2:password2` (while the previous connection is still alive) - the second request wrongly reused the same connection and since it then sees that the Negotiate negotiation is already made, it just sends the request over that connection thinking it uses the user2 credentials when it is in fact still using the connection authenticated for user1... The set of authentication methods to use is set with `CURLOPT_HTTPAUTH`. Applications can disable libcurl's reuse of connections and thus mitigate this problem, by using one of the following libcurl options to alter how connections are or are not reused: `CURLOPT_FRESH_CONNECT`, `CURLOPT_MAXCONNECTS` and `CURLMOPT_MAX_HOST_CONNECTIONS` (if using the curl_multi API). CVE-2026-1965 Container private-registry/harbor-trivy-adapter:latest:libcurl4-8.14.1-150700.7.14.1 Image pr_15_7:libcurl4-8.14.1-150700.7.14.1 SUSE Linux Enterprise Module for Basesystem 15 SP7:curl-8.14.1-150700.7.14.1 SUSE Linux Enterprise Module for Basesystem 15 SP7:libcurl-devel-8.14.1-150700.7.14.1 SUSE Linux Enterprise Module for Basesystem 15 SP7:libcurl4-32bit-8.14.1-150700.7.14.1 SUSE Linux Enterprise Module for Basesystem 15 SP7:libcurl4-8.14.1-150700.7.14.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260903-1/ https://www.suse.com/security/cve/CVE-2026-1965.html CVE-2026-1965 https://bugzilla.suse.com/1259362 SUSE Bug 1259362 When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a redirect to a second URL, curl could leak that token to the second hostname under some circumstances. If the hostname that the first request is redirected to has information in the used .netrc file, with either of the `machine` or `default` keywords, curl would pass on the bearer token set for the first host also to the second one. CVE-2026-3783 Container private-registry/harbor-trivy-adapter:latest:libcurl4-8.14.1-150700.7.14.1 Image pr_15_7:libcurl4-8.14.1-150700.7.14.1 SUSE Linux Enterprise Module for Basesystem 15 SP7:curl-8.14.1-150700.7.14.1 SUSE Linux Enterprise Module for Basesystem 15 SP7:libcurl-devel-8.14.1-150700.7.14.1 SUSE Linux Enterprise Module for Basesystem 15 SP7:libcurl4-32bit-8.14.1-150700.7.14.1 SUSE Linux Enterprise Module for Basesystem 15 SP7:libcurl4-8.14.1-150700.7.14.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260903-1/ https://www.suse.com/security/cve/CVE-2026-3783.html CVE-2026-3783 https://bugzilla.suse.com/1259363 SUSE Bug 1259363 curl would wrongly reuse an existing HTTP proxy connection doing CONNECT to a server, even if the new request uses different credentials for the HTTP proxy. The proper behavior is to create or use a separate connection. CVE-2026-3784 Container private-registry/harbor-trivy-adapter:latest:libcurl4-8.14.1-150700.7.14.1 Image pr_15_7:libcurl4-8.14.1-150700.7.14.1 SUSE Linux Enterprise Module for Basesystem 15 SP7:curl-8.14.1-150700.7.14.1 SUSE Linux Enterprise Module for Basesystem 15 SP7:libcurl-devel-8.14.1-150700.7.14.1 SUSE Linux Enterprise Module for Basesystem 15 SP7:libcurl4-32bit-8.14.1-150700.7.14.1 SUSE Linux Enterprise Module for Basesystem 15 SP7:libcurl4-8.14.1-150700.7.14.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260903-1/ https://www.suse.com/security/cve/CVE-2026-3784.html CVE-2026-3784 https://bugzilla.suse.com/1259364 SUSE Bug 1259364 When doing a second SMB request to the same host again, curl would wrongly use a data pointer pointing into already freed memory. CVE-2026-3805 Container private-registry/harbor-trivy-adapter:latest:libcurl4-8.14.1-150700.7.14.1 Image pr_15_7:libcurl4-8.14.1-150700.7.14.1 SUSE Linux Enterprise Module for Basesystem 15 SP7:curl-8.14.1-150700.7.14.1 SUSE Linux Enterprise Module for Basesystem 15 SP7:libcurl-devel-8.14.1-150700.7.14.1 SUSE Linux Enterprise Module for Basesystem 15 SP7:libcurl4-32bit-8.14.1-150700.7.14.1 SUSE Linux Enterprise Module for Basesystem 15 SP7:libcurl4-8.14.1-150700.7.14.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2026/suse-su-20260903-1/ https://www.suse.com/security/cve/CVE-2026-3805.html CVE-2026-3805 https://bugzilla.suse.com/1259365 SUSE Bug 1259365