Debian Curl vulnerabilities

CVE-2026-3784 [MEDIUM] CVE-2026-3784: curl - curl would wrongly reuse an existing HTTP proxy connection doing CONNECT to a se... 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. Scope: local bookworm: open bullseye: open forky: resolved (fixed in 8.19.0-1) sid: resolved (fixed in 8.19.0-1) trixie: open

CVE-2026-1965 [MEDIUM] CVE-2026-1965: curl - libcurl can in some circumstances reuse the wrong connection when asked to do an... 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

CVE-2026-3783 [MEDIUM] CVE-2026-3783: curl - When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer p... 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

CVE-2026-3805 [HIGH] CVE-2026-3805: curl - When doing a second SMB request to the same host again, curl would wrongly use a... When doing a second SMB request to the same host again, curl would wrongly use a data pointer pointing into already freed memory. Scope: local bookworm: resolved bullseye: resolved forky: resolved (fixed in 8.19.0-1) sid: resolved (fixed in 8.19.0-1) trixie: open

CVE-2025-14819 [MEDIUM] CVE-2025-14819: curl - When doing TLS related transfers with reused easy or multi handles and altering ... 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. This could make libcurl find and accept a trust chain that it otherwise would not. Scope:

CVE-2025-14524 [MEDIUM] CVE-2025-14524: curl - When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer p... 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. Scope: local bookworm: open bullseye: open forky: resolved (fixed in 8.18.0~rc2-1) sid: resolved (fixed in 8.18.0~rc2-1) trix

CVE-2025-10148 [MEDIUM] CVE-2025-10148: curl - curl's websocket code did not update the 32 bit mask pattern for each new outgo... 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 traffic between the two communicating parties that could be interpreted by an involved proxy (c

CVE-2025-5025 [MEDIUM] CVE-2025-5025: curl - libcurl supports *pinning* of the server certificate public key for HTTPS transf... 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 does not for QUIC and HTTP/3. Since pinning makes the transfer succeed if the pin is fine,

CVE-2025-5399 [HIGH] CVE-2025-5399: curl - Due to a mistake in libcurl's WebSocket code, a malicious server can send a part... 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 might be used to DoS libcurl-using application. Scope: local bookworm: resolved bullseye: resolved

CVE-2025-14017 [MEDIUM] CVE-2025-14017: curl - When doing multi-threaded LDAPS transfers (LDAP over TLS) with libcurl, changing... 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 could unintentionally disable the feature for other threads as well. Scope: local bookworm:

CVE-2025-11563 [MEDIUM] CVE-2025-11563: curl - URLs containing percent-encoded slashes (`/` or `\`) can trick wcurl into saving... 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. Scope: local bookworm: resolved bullseye: resolved forky: resolved (fixed in 8.17.0-2) sid: resolved (fixed in 8.17.0-2) trixie: resolved (fixed

CVE-2025-0167 [LOW] CVE-2025-0167: curl - When asked to use a `.netrc` file for credentials **and** to follow HTTP redirec... When asked to use a `.netrc` file for credentials **and** to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances. This flaw only manifests itself if the netrc file has a `default` entry that omits both login and password. A rare circumstance. Scope: local bookworm: resolved (fixed in 7.88.1-10+deb

CVE-2025-4947 [MEDIUM] CVE-2025-4947: curl - libcurl accidentally skips the certificate verification for QUIC connections whe... 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. Scope: local bookworm: resolved bullseye: resolved forky: resolved (fixed in 8.14.0-1) sid: resolved (fixed in 8.14.0-1) trixie: resolved (fixed in 8.14.0-1)

CVE-2025-9086 [HIGH] CVE-2025-9086: curl - 1. A cookie is set using the `secure` keyword for `https://target` 2. curl is ... 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 (`path=\"/\",`). Since this site is not secure, the cookie *should* just be ignored. 4. A bug in the

CVE-2025-13034 [MEDIUM] CVE-2025-13034: curl - When using `CURLOPT_PINNEDPUBLICKEY` option with libcurl or `--pinnedpubkey` wit... When using `CURLOPT_PINNEDPUBLICKEY` option with libcurl or `--pinnedpubkey` with the curl tool,curl should check the public key of the server certificate to verify the peer. This check was skipped in a certain condition that would then make curl allow the connection without performing the proper check, thus not noticing a possible impostor. To skip this check, the c

CVE-2025-10966 [MEDIUM] CVE-2025-10966: curl - curl's code for managing SSH connections when SFTP was done using the wolfSSH po... curl's code for managing SSH connections when SFTP was done using the wolfSSH powered backend was flawed and missed host verification mechanisms. This prevents curl from detecting MITM attackers and more. Scope: local bookworm: open bullseye: open forky: resolved (fixed in 8.17.0~rc2-1) sid: resolved (fixed in 8.17.0~rc2-1) trixie: open

CVE-2025-15079 [MEDIUM] CVE-2025-15079: curl - When doing SSH-based transfers using either SCP or SFTP, and setting the known_h... 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. Scope: local bookworm: open bullseye: open forky: resolved (fixed in 8.18.0~rc3-1) sid: resolved (fixed in 8.1

CVE-2025-0665 [HIGH] CVE-2025-0665: curl - libcurl would wrongly close the same eventfd file descriptor twice when taking d... libcurl would wrongly close the same eventfd file descriptor twice when taking down a connection channel after having completed a threaded name resolve. Scope: local bookworm: resolved bullseye: resolved forky: resolved (fixed in 8.12.0+git20250209.89ed161+ds-1) sid: resolved (fixed in 8.12.0+git20250209.89ed161+ds-1) trixie: resolved (fixed in 8.12.0+git20250209.89ed161

CVE-2025-0725 [HIGH] CVE-2025-0725: curl - When libcurl is asked to perform automatic gzip decompression of content-encoded... When libcurl is asked to perform automatic gzip decompression of content-encoded HTTP responses with the `CURLOPT_ACCEPT_ENCODING` option, **using zlib 1.2.0.3 or older**, an attacker-controlled integer overflow would make libcurl perform a buffer overflow. Scope: local bookworm: open bullseye: open forky: resolved (fixed in 8.12.0+git20250209.89ed161+ds-1) sid: resolved

CVE-2025-15224 [LOW] CVE-2025-15224: curl - When doing SSH-based transfers using either SCP or SFTP, and asked to do public ... 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. Scope: local bookworm: open bullseye: open forky: resolved (fixed in 8.18.0-1) sid: resolved (fixed in 8.18.0-1) trixie: open