rpm package
almalinux/curl-minimal
pkg:rpm/almalinux/curl-minimal
Vulnerabilities (29)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-9547 | Hig | 7.4 | < 7.76.1-40.el9_8.5 | 7.76.1-40.el9_8.5 | Jul 3, 2026 | When a libcurl-based application performs transfers via `SCP://` or `SFTP://` and utilizes the `CURLOPT_SSH_KEYFUNCTION` callback, it may silently accept an untrusted server. This vulnerability occurs when a server presents a host key type that does not match the specific key typ | |
| CVE-2026-8932 | Hig | 7.5 | < 7.76.1-40.el9_8.9 | 7.76.1-40.el9_8.9 | Jul 3, 2026 | libcurl would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse. libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. Ho | |
| CVE-2026-8927 | Cri | 9.1 | < 7.76.1-40.el9_8.7 | 7.76.1-40.el9_8.7 | Jul 3, 2026 | When reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentication state between requests. Specifically, if the initial transfer authenticates against `proxyA` using Digest auth, a subsequent | |
| CVE-2026-8924 | Cri | 9.1 | < 7.76.1-40.el9_8.8 | 7.76.1-40.el9_8.8 | Jul 3, 2026 | A flaw in curl’s cookie parsing logic allows a malicious HTTP server to set "super cookies" that bypass the Public Suffix List check. This enables an attacker-controlled origin to inject cookies that curl subsequently scopes and transmits to unrelated third-party domains. | |
| CVE-2026-8458 | Med | 6.5 | < 7.76.1-40.el9_8.7 | 7.76.1-40.el9_8.7 | Jul 3, 2026 | libcurl might in some circumstances reuse the wrong connection when asked to do Negotiate-authenticated ones, even when they are set to use different "services". libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid o | |
| CVE-2026-8286 | Hig | 8.1 | < 7.76.1-40.el9_8.5 | 7.76.1-40.el9_8.5 | Jul 3, 2026 | A vulnerability exists where a new transfer that uses STARTTLS to upgrade the connection might reuse an existing live connection even though the TLS configuration mismatches so it should not. | |
| CVE-2026-11856 | Cri | 9.8 | < 7.76.1-40.el9_8.8 | 7.76.1-40.el9_8.8 | Jul 3, 2026 | Successfully using libcurl to do a transfer to a specific HTTP origin (`hostA`) with **Digest** authentication and then changing the origin to a different one (`hostB`) for a second transfer, reusing the same handle, makes libcurl wrongly pass on the `Authorization:` header field | |
| CVE-2026-3783 | Med | 5.3 | < 7.76.1-40.el9_8.5 | 7.76.1-40.el9_8.5 | 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 | Med | 6.5 | < 7.76.1-40.el9_8.5 | 7.76.1-40.el9_8.5 | 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-9086 | Hig | 7.5 | < 7.76.1-35.el9_7.3 | 7.76.1-35.el9_7.3 | 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 only a slash as path (`pat | |
| CVE-2024-2398 | Hig | 8.6 | < 7.76.1-29.el9_4.1 | 7.76.1-29.el9_4.1 | Mar 27, 2024 | When an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts the server push. When aborting, libcurl inadvertently does not free all the previously allocated head | |
| CVE-2023-46218 | Med | 6.5 | < 7.76.1-26.el9_3.3 | 7.76.1-26.el9_3.3 | Dec 7, 2023 | This flaw allows a malicious HTTP server to set "super cookies" in curl that are then passed back to more origins than what is otherwise allowed or possible. This allows a site to set cookies that then would get sent to different and unrelated sites and domains. It could do this | |
| CVE-2023-38546 | Low | 3.7 | < 7.76.1-23.el9_2.4 | 7.76.1-23.el9_2.4 | Oct 18, 2023 | This flaw allows an attacker to insert cookies at will into a running program using libcurl, if the specific series of conditions are met. libcurl performs transfers. In its API, an application creates "easy handles" that are the individual handles for single transfers. libcurl | |
| CVE-2023-38545 | Cri | 9.8 | < 7.76.1-23.el9_2.4 | 7.76.1-23.el9_2.4 | Oct 18, 2023 | This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that host name can be is 255 byt | |
| CVE-2023-28322 | Low | 3.7 | < 7.76.1-23.el9_2.2 | 7.76.1-23.el9_2.2 | May 26, 2023 | An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle previously was | |
| CVE-2023-28321 | Med | 5.9 | < 7.76.1-23.el9_2.2 | 7.76.1-23.el9_2.2 | May 26, 2023 | An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of wildcard patterns when listed as "Subject Alternative Name" in TLS server certificates. curl can be built to use its own name matching function for TLS rather than one provi | |
| CVE-2023-27538 | Med | 5.5 | < 7.76.1-26.el9 | 7.76.1-26.el9 | Mar 30, 2023 | An authentication bypass vulnerability exists in libcurl prior to v8.0.0 where it reuses a previously established SSH connection despite the fact that an SSH option was modified, which should have prevented reuse. libcurl maintains a pool of previously used connections to reuse t | |
| CVE-2023-27536 | Med | 5.9 | < 7.76.1-26.el9 | 7.76.1-26.el9 | Mar 30, 2023 | An authentication bypass vulnerability exists libcurl <8.0.0 in the connection reuse feature which can reuse previously established connections with incorrect user permissions due to a failure to check for changes in the CURLOPT_GSSAPI_DELEGATION option. This vulnerability affect | |
| CVE-2023-27535 | Med | 5.9 | < 7.76.1-23.el9_2.1 | 7.76.1-23.el9_2.1 | Mar 30, 2023 | An authentication bypass vulnerability exists in libcurl <8.0.0 in the FTP connection reuse feature that can result in wrong credentials being used during subsequent transfers. Previously created connections are kept in a connection pool for reuse if they match the current setup. | |
| CVE-2023-27534 | Hig | 8.8 | < 7.76.1-26.el9 | 7.76.1-26.el9 | Mar 30, 2023 | A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde (~) character to be wrongly replaced when used as a prefix in the first path element, in addition to its intended use as the first element to indicate a path relative to the user's home dire |
- affected < 7.76.1-40.el9_8.5fixed 7.76.1-40.el9_8.5
When a libcurl-based application performs transfers via `SCP://` or `SFTP://` and utilizes the `CURLOPT_SSH_KEYFUNCTION` callback, it may silently accept an untrusted server. This vulnerability occurs when a server presents a host key type that does not match the specific key typ
- affected < 7.76.1-40.el9_8.9fixed 7.76.1-40.el9_8.9
libcurl would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse. libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. Ho
- affected < 7.76.1-40.el9_8.7fixed 7.76.1-40.el9_8.7
When reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentication state between requests. Specifically, if the initial transfer authenticates against `proxyA` using Digest auth, a subsequent
- affected < 7.76.1-40.el9_8.8fixed 7.76.1-40.el9_8.8
A flaw in curl’s cookie parsing logic allows a malicious HTTP server to set "super cookies" that bypass the Public Suffix List check. This enables an attacker-controlled origin to inject cookies that curl subsequently scopes and transmits to unrelated third-party domains.
- affected < 7.76.1-40.el9_8.7fixed 7.76.1-40.el9_8.7
libcurl might in some circumstances reuse the wrong connection when asked to do Negotiate-authenticated ones, even when they are set to use different "services". libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid o
- affected < 7.76.1-40.el9_8.5fixed 7.76.1-40.el9_8.5
A vulnerability exists where a new transfer that uses STARTTLS to upgrade the connection might reuse an existing live connection even though the TLS configuration mismatches so it should not.
- affected < 7.76.1-40.el9_8.8fixed 7.76.1-40.el9_8.8
Successfully using libcurl to do a transfer to a specific HTTP origin (`hostA`) with **Digest** authentication and then changing the origin to a different one (`hostB`) for a second transfer, reusing the same handle, makes libcurl wrongly pass on the `Authorization:` header field
- affected < 7.76.1-40.el9_8.5fixed 7.76.1-40.el9_8.5
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
- affected < 7.76.1-40.el9_8.5fixed 7.76.1-40.el9_8.5
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
- affected < 7.76.1-35.el9_7.3fixed 7.76.1-35.el9_7.3
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 slash as path (`pat
- affected < 7.76.1-29.el9_4.1fixed 7.76.1-29.el9_4.1
When an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts the server push. When aborting, libcurl inadvertently does not free all the previously allocated head
- affected < 7.76.1-26.el9_3.3fixed 7.76.1-26.el9_3.3
This flaw allows a malicious HTTP server to set "super cookies" in curl that are then passed back to more origins than what is otherwise allowed or possible. This allows a site to set cookies that then would get sent to different and unrelated sites and domains. It could do this
- affected < 7.76.1-23.el9_2.4fixed 7.76.1-23.el9_2.4
This flaw allows an attacker to insert cookies at will into a running program using libcurl, if the specific series of conditions are met. libcurl performs transfers. In its API, an application creates "easy handles" that are the individual handles for single transfers. libcurl
- affected < 7.76.1-23.el9_2.4fixed 7.76.1-23.el9_2.4
This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that host name can be is 255 byt
- affected < 7.76.1-23.el9_2.2fixed 7.76.1-23.el9_2.2
An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle previously was
- affected < 7.76.1-23.el9_2.2fixed 7.76.1-23.el9_2.2
An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of wildcard patterns when listed as "Subject Alternative Name" in TLS server certificates. curl can be built to use its own name matching function for TLS rather than one provi
- affected < 7.76.1-26.el9fixed 7.76.1-26.el9
An authentication bypass vulnerability exists in libcurl prior to v8.0.0 where it reuses a previously established SSH connection despite the fact that an SSH option was modified, which should have prevented reuse. libcurl maintains a pool of previously used connections to reuse t
- affected < 7.76.1-26.el9fixed 7.76.1-26.el9
An authentication bypass vulnerability exists libcurl <8.0.0 in the connection reuse feature which can reuse previously established connections with incorrect user permissions due to a failure to check for changes in the CURLOPT_GSSAPI_DELEGATION option. This vulnerability affect
- affected < 7.76.1-23.el9_2.1fixed 7.76.1-23.el9_2.1
An authentication bypass vulnerability exists in libcurl <8.0.0 in the FTP connection reuse feature that can result in wrong credentials being used during subsequent transfers. Previously created connections are kept in a connection pool for reuse if they match the current setup.
- affected < 7.76.1-26.el9fixed 7.76.1-26.el9
A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde (~) character to be wrongly replaced when used as a prefix in the first path element, in addition to its intended use as the first element to indicate a path relative to the user's home dire
Page 1 of 2