Bugs fixes in "curl"
| Origin | Bug number | Title | Date fixed |
|---|---|---|---|
| CVE | CVE-2026-92388 | When an FTP wildcard `LIST` operation fails, libcurl omits the restoration path meant for successful listings, leaving the write callback set to the | 2026-10-21 |
| CVE | CVE-2026-92387 | By permanently omitting the final control-response line, a malicious FTP, IMAP, POP3, or SMTP server can exploit libcurl and completely bypass its co | 2026-10-21 |
| CVE | CVE-2026-92386 | When writing a long cookie name and value to a Netscape cookie jar, a remote HTTP server can make `curl` write a record that exceeds its line-length | 2026-10-21 |
| CVE | CVE-2026-87865 | When libcurl uses libssh2 with a hashed `known_hosts` file, an unrelated initial entry can cause host key validation to report a key *mismatch* as a | 2026-10-21 |
| CVE | CVE-2026-87864 | Enabling `CURLOPT_CRLF` causes curl to advertise the raw input byte count in the `IMAP APPEND {N}` literal while transmitting line-ending expanded da | 2026-10-21 |
| CVE | CVE-2026-87863 | An authenticated HTTPS origin can supply an HSTS `max-age` value that the parser accepts, but time serialization later fails to process. On 64-bit sy | 2026-10-21 |
| CVE | CVE-2026-87862 | Importing a `includeSubDomains` parent HSTS entry before a longer-lived child entry, silently drops the child. Consequently, when the parent expires, | 2026-10-21 |
| CVE | CVE-2026-86414 | An HTTP proxy can trick libcurl into sending the origin's credentials (Basic password, or a Negotiate/Kerberos ticket) to the proxy itself, by answer | 2026-10-21 |
| CVE | CVE-2026-86412 | A remote HTTP server can set a cookie that curl accepts and writes to a Netscape cookie jar but cannot reload. On the next invocation using the same | 2026-10-21 |
| CVE | CVE-2026-86410 | A flaw in the curl command line tool's logic makes it only set SSH host verification options when interacting directly using SFTP or SCP, and not as | 2026-10-21 |
| CVE | CVE-2026-86409 | Setting `CURLOPT_AWS_SIGV4` to NULL but does not disable SigV4 authentication, contrary to expectations and documentation. A subsequent transfer on t | 2026-10-21 |
| CVE | CVE-2026-107929 | When `CURLOPT_INTERFACE` (or the command line tool's `--interface` option) is set with one of the documented prefixes (`if!`, `host!`, `ifhost!`), th | 2026-10-21 |
| CVE | CVE-2026-107928 | When curl is built with GnuTLS, a malicious WebSocket server can make curl send memory past its send buffer. This is due to an out of bounds read fol | 2026-10-21 |
| CVE | CVE-2026-92392 | During an upload, curl mishandles HTTP/2 `RST_STREAM` received from the server (with reason `HTTP_1_1_REQUIRED` or `REFUSED_STREAM`) leading to a use | 2026-10-19 |
| CVE | CVE-2026-8932 | libcurl would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse. li | 2026-09-24 |
| CVE | CVE-2026-8458 | libcurl might in some circumstances reuse the wrong connection when asked to do Negotiate-authenticated ones, even when they are set to use different | 2026-09-24 |
| CVE | CVE-2026-6429 | 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 f | 2026-09-24 |
| CVE | CVE-2026-8927 | When reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentic | 2026-09-24 |
| CVE | CVE-2026-82209 | When libpsl support is enabled, libcurl fails to enforce the Public Suffix List boundary check when processing a `Set-Cookie` header where the `Domai | 2026-09-24 |
| CVE | CVE-2026-80230 | When `CURLOPT_PINNEDPUBLICKEY` is configured alongside options that disable standard peer verification (`CURLOPT_SSL_VERIFYPEER = 0` and `CURLOPT_SSL | 2026-09-24 |
About
-
Send Feedback to @ubuntu_updates