Fixed packages 4
| Release | Package | Fixed in |
|---|---|---|
| Red Hat · Hardened Images 1 hummingbird:1 | curl | 0:8.19.0-3.hum1 |
| Red Hat · Hardened Images 1 hummingbird:1 | libcurl | 0:8.19.0-3.hum1 |
| Red Hat · Hardened Images 1 hummingbird:1 | libcurl-devel | 0:8.19.0-3.hum1 |
| Red Hat · Hardened Images 1 hummingbird:1 | libcurl-minimal | 0:8.19.0-3.hum1 |
Vulnerabilities 13
-
High 7.5
Out of bounds read for cookie path
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 only a s…
-
High 7.5CVE-2026-3805 Public exploit
use after free in SMB connection reuse
When doing a second SMB request to the same host again, curl would wrongly use a data pointer pointing into already freed memory.
-
Medium 6.5
bad reuse of HTTP Negotiate connection
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 …
-
Medium 6.5
wrong proxy connection reuse with credentials
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.
-
Medium 6.3
broken TLS options for threaded LDAPS
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…
-
Medium 5.9
No QUIC certificate pinning with GnuTLS
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 c…
-
Medium 5.3
predictable WebSocket mask
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 se…
-
Medium 5.3
bearer token leak on cross-protocol redirect
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.
-
Medium 5.3
OpenSSL partial chain store policy bypass
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 wishe…
-
Medium 5.3
libssh global known_hosts override
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.
-
Medium 5.3
token leak with redirect and netrc
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 informa…
-
Medium 4.3
missing SFTP host verification with wolfSSH
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.
-
Low 3.1
libssh key passphrase bypass without agent set
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.
References
-
article
https://images.redhat.com/
-
report
https://access.redhat.com/security/cve/CVE-2025-9086
-
article
https://access.redhat.com/security/updates/classification/
-
report
https://access.redhat.com/security/cve/CVE-2025-10148
-
report
https://access.redhat.com/security/cve/CVE-2025-10966
-
report
https://access.redhat.com/security/cve/CVE-2025-15224
-
report
https://access.redhat.com/security/cve/CVE-2025-15079
-
report
https://access.redhat.com/security/cve/CVE-2025-14819
-
report
https://access.redhat.com/security/cve/CVE-2025-14524
-
report
https://access.redhat.com/security/cve/CVE-2025-13034
-
report
https://access.redhat.com/security/cve/CVE-2026-3805
-
report
https://access.redhat.com/security/cve/CVE-2026-3783
-
report
https://access.redhat.com/security/cve/CVE-2026-3784
-
report
https://access.redhat.com/security/cve/CVE-2026-1965
-
report
https://access.redhat.com/security/cve/CVE-2025-14017
-
advisory
https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_6893.json
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2394750
-
advisory
https://www.cve.org/CVERecord?id=CVE-2025-9086
-
advisory
https://nvd.nist.gov/vuln/detail/CVE-2025-9086
-
article
https://curl.se/docs/CVE-2025-9086.html
-
article
https://curl.se/docs/CVE-2025-9086.json
-
article
https://github.com/curl/curl/commit/c6ae07c6a541e0e96d0040afb6
-
article
https://hackerone.com/reports/3294999
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2394749
-
advisory
https://www.cve.org/CVERecord?id=CVE-2025-10148
-
advisory
https://nvd.nist.gov/vuln/detail/CVE-2025-10148
-
article
https://curl.se/docs/CVE-2025-10148.html
-
article
https://curl.se/docs/CVE-2025-10148.json
-
article
https://hackerone.com/reports/3330839
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2413308
-
advisory
https://www.cve.org/CVERecord?id=CVE-2025-10966
-
advisory
https://nvd.nist.gov/vuln/detail/CVE-2025-10966
-
article
http://www.openwall.com/lists/oss-security/2025/11/05/2
-
article
https://curl.se/docs/CVE-2025-10966.html
-
article
https://curl.se/docs/CVE-2025-10966.json
-
article
https://github.com/curl/curl/commit/b011e3fcfb06d6c027859
-
article
https://hackerone.com/reports/3355218
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2426406
-
advisory
https://www.cve.org/CVERecord?id=CVE-2025-13034