rpm package
suse/curl&distro=SUSE Linux Enterprise Module for Basesystem 15 SP7
pkg:rpm/suse/curl&distro=SUSE%20Linux%20Enterprise%20Module%20for%20Basesystem%2015%20SP7
Vulnerabilities (17)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-3784 | Med | 6.5 | < 8.14.1-150700.7.14.1 | 8.14.1-150700.7.14.1 | Mar 11, 2026 | 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-3805 | — | < 8.14.1-150700.7.14.1 | 8.14.1-150700.7.14.1 | Mar 11, 2026 | 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-3783 | — | < 8.14.1-150700.7.14.1 | 8.14.1-150700.7.14.1 | Mar 11, 2026 | 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 .ne | ||
| CVE-2026-1965 | — | < 8.14.1-150700.7.14.1 | 8.14.1-150700.7.14.1 | Mar 11, 2026 | 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 connectio | ||
| CVE-2025-11563 | — | < 8.14.1-150700.7.5.1 | 8.14.1-150700.7.5.1 | Feb 25, 2026 | URLs containing percent-encoded slashes (`/` or `\`) can trick wcurl into saving the output file outside of the current directory without the user explicitly asking for it. This flaw only affects the wcurl command line tool. | ||
| CVE-2025-15224 | — | < 8.14.1-150700.7.8.1 | 8.14.1-150700.7.8.1 | Jan 8, 2026 | When doing SSH-based transfers using either SCP or SFTP, and asked to do public key authentication, curl would wrongly still ask and authenticate using a locally running SSH agent. | ||
| CVE-2025-15079 | — | < 8.14.1-150700.7.8.1 | 8.14.1-150700.7.8.1 | Jan 8, 2026 | When doing SSH-based transfers using either SCP or SFTP, and setting the known_hosts file, libcurl could still mistakenly accept connecting to hosts *not present* in the specified file if they were added as recognized in the libssh *global* known_hosts file. | ||
| CVE-2025-14819 | — | < 8.14.1-150700.7.8.1 | 8.14.1-150700.7.8.1 | Jan 8, 2026 | When doing TLS related transfers with reused easy or multi handles and altering the `CURLSSLOPT_NO_PARTIALCHAIN` option, libcurl could accidentally reuse a CA store cached in memory for which the partial chain option was reversed. Contrary to the user's wishes and expectations. | ||
| CVE-2025-14524 | — | < 8.14.1-150700.7.8.1 | 8.14.1-150700.7.8.1 | Jan 8, 2026 | When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a cross-protocol redirect to a second URL that uses an IMAP, LDAP, POP3 or SMTP scheme, curl might wrongly pass on the bearer token to the new target host. | ||
| CVE-2025-14017 | — | < 8.14.1-150700.7.11.1 | 8.14.1-150700.7.11.1 | Jan 8, 2026 | When doing multi-threaded LDAPS transfers (LDAP over TLS) with libcurl, changing TLS options in one thread would inadvertently change them globally and therefore possibly also affect other concurrently setup transfers. Disabling certificate verification for a specific transfer c | ||
| CVE-2025-9086 | Hig | 7.5 | < 8.14.1-150600.4.28.1 | 8.14.1-150600.4.28.1 | Sep 12, 2025 | 1. A cookie is set using the `secure` keyword for `https://target` 2. curl is redirected to or otherwise made to speak with `http://target` (same hostname, but using clear text HTTP) using the same cookie set 3. The same cookie name is set - but with just a slash as path | |
| CVE-2025-10148 | — | < 8.14.1-150600.4.28.1 | 8.14.1-150600.4.28.1 | Sep 12, 2025 | curl's websocket code did not update the 32 bit mask pattern for each new outgoing frame as the specification says. Instead it used a fixed mask that persisted and was used throughout the entire connection. A predictable mask pattern allows for a malicious server to induce traf | ||
| CVE-2025-5399 | — | < 8.14.1-150600.4.28.1 | 8.14.1-150600.4.28.1 | Jun 7, 2025 | Due to a mistake in libcurl's WebSocket code, a malicious server can send a particularly crafted packet which makes libcurl get trapped in an endless busy-loop. There is no other way for the application to escape or exit this loop other than killing the thread/process. This mig | ||
| CVE-2025-5025 | — | < 8.14.1-150600.4.28.1 | 8.14.1-150600.4.28.1 | May 28, 2025 | libcurl supports *pinning* of the server certificate public key for HTTPS transfers. Due to an omission, this check is not performed when connecting with QUIC for HTTP/3, when the TLS backend is wolfSSL. Documentation says the option works with wolfSSL, failing to specify that it | ||
| CVE-2025-4947 | — | < 8.14.1-150600.4.28.1 | 8.14.1-150600.4.28.1 | May 28, 2025 | libcurl accidentally skips the certificate verification for QUIC connections when connecting to a host specified as an IP address in the URL. Therefore, it does not detect impostors or man-in-the-middle attacks. | ||
| CVE-2025-0665 | — | < 8.14.1-150600.4.28.1 | 8.14.1-150600.4.28.1 | Feb 5, 2025 | libcurl would wrongly close the same eventfd file descriptor twice when taking down a connection channel after having completed a threaded name resolve. | ||
| CVE-2024-6874 | — | < 8.14.1-150600.4.28.1 | 8.14.1-150600.4.28.1 | Jul 24, 2024 | libcurl's URL API function [curl_url_get()](https://curl.se/libcurl/c/curl_url_get.html) offers punycode conversions, to and from IDN. Asking to convert a name that is exactly 256 bytes, libcurl ends up reading outside of a stack based buffer when built to use the *macidn* IDN ba |
- affected < 8.14.1-150700.7.14.1fixed 8.14.1-150700.7.14.1
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-3805Mar 11, 2026affected < 8.14.1-150700.7.14.1fixed 8.14.1-150700.7.14.1
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-3783Mar 11, 2026affected < 8.14.1-150700.7.14.1fixed 8.14.1-150700.7.14.1
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 .ne
- CVE-2026-1965Mar 11, 2026affected < 8.14.1-150700.7.14.1fixed 8.14.1-150700.7.14.1
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 connectio
- CVE-2025-11563Feb 25, 2026affected < 8.14.1-150700.7.5.1fixed 8.14.1-150700.7.5.1
URLs containing percent-encoded slashes (`/` or `\`) can trick wcurl into saving the output file outside of the current directory without the user explicitly asking for it. This flaw only affects the wcurl command line tool.
- CVE-2025-15224Jan 8, 2026affected < 8.14.1-150700.7.8.1fixed 8.14.1-150700.7.8.1
When doing SSH-based transfers using either SCP or SFTP, and asked to do public key authentication, curl would wrongly still ask and authenticate using a locally running SSH agent.
- CVE-2025-15079Jan 8, 2026affected < 8.14.1-150700.7.8.1fixed 8.14.1-150700.7.8.1
When doing SSH-based transfers using either SCP or SFTP, and setting the known_hosts file, libcurl could still mistakenly accept connecting to hosts *not present* in the specified file if they were added as recognized in the libssh *global* known_hosts file.
- CVE-2025-14819Jan 8, 2026affected < 8.14.1-150700.7.8.1fixed 8.14.1-150700.7.8.1
When doing TLS related transfers with reused easy or multi handles and altering the `CURLSSLOPT_NO_PARTIALCHAIN` option, libcurl could accidentally reuse a CA store cached in memory for which the partial chain option was reversed. Contrary to the user's wishes and expectations.
- CVE-2025-14524Jan 8, 2026affected < 8.14.1-150700.7.8.1fixed 8.14.1-150700.7.8.1
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a cross-protocol redirect to a second URL that uses an IMAP, LDAP, POP3 or SMTP scheme, curl might wrongly pass on the bearer token to the new target host.
- CVE-2025-14017Jan 8, 2026affected < 8.14.1-150700.7.11.1fixed 8.14.1-150700.7.11.1
When doing multi-threaded LDAPS transfers (LDAP over TLS) with libcurl, changing TLS options in one thread would inadvertently change them globally and therefore possibly also affect other concurrently setup transfers. Disabling certificate verification for a specific transfer c
- affected < 8.14.1-150600.4.28.1fixed 8.14.1-150600.4.28.1
1. A cookie is set using the `secure` keyword for `https://target` 2. curl is redirected to or otherwise made to speak with `http://target` (same hostname, but using clear text HTTP) using the same cookie set 3. The same cookie name is set - but with just a slash as path
- CVE-2025-10148Sep 12, 2025affected < 8.14.1-150600.4.28.1fixed 8.14.1-150600.4.28.1
curl's websocket code did not update the 32 bit mask pattern for each new outgoing frame as the specification says. Instead it used a fixed mask that persisted and was used throughout the entire connection. A predictable mask pattern allows for a malicious server to induce traf
- CVE-2025-5399Jun 7, 2025affected < 8.14.1-150600.4.28.1fixed 8.14.1-150600.4.28.1
Due to a mistake in libcurl's WebSocket code, a malicious server can send a particularly crafted packet which makes libcurl get trapped in an endless busy-loop. There is no other way for the application to escape or exit this loop other than killing the thread/process. This mig
- CVE-2025-5025May 28, 2025affected < 8.14.1-150600.4.28.1fixed 8.14.1-150600.4.28.1
libcurl supports *pinning* of the server certificate public key for HTTPS transfers. Due to an omission, this check is not performed when connecting with QUIC for HTTP/3, when the TLS backend is wolfSSL. Documentation says the option works with wolfSSL, failing to specify that it
- CVE-2025-4947May 28, 2025affected < 8.14.1-150600.4.28.1fixed 8.14.1-150600.4.28.1
libcurl accidentally skips the certificate verification for QUIC connections when connecting to a host specified as an IP address in the URL. Therefore, it does not detect impostors or man-in-the-middle attacks.
- CVE-2025-0665Feb 5, 2025affected < 8.14.1-150600.4.28.1fixed 8.14.1-150600.4.28.1
libcurl would wrongly close the same eventfd file descriptor twice when taking down a connection channel after having completed a threaded name resolve.
- CVE-2024-6874Jul 24, 2024affected < 8.14.1-150600.4.28.1fixed 8.14.1-150600.4.28.1
libcurl's URL API function [curl_url_get()](https://curl.se/libcurl/c/curl_url_get.html) offers punycode conversions, to and from IDN. Asking to convert a name that is exactly 256 bytes, libcurl ends up reading outside of a stack based buffer when built to use the *macidn* IDN ba