Search for packages
| purl | pkg:generic/curl.se/curl@8.5.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-1ypr-54n1-27hn
Aliases: CVE-2024-8096 |
When curl is told to use the Certificate Status Request TLS extension, often referred to as OCSP stapling, to verify that the server certificate is valid, it might fail to detect some OCSP problems and instead wrongly consider the response as fine. If the returned status reports another error than 'revoked' (like for example 'unauthorized') it is not treated as a bad certficate. |
Affected by 8 other vulnerabilities. |
|
VCID-4g24-wxrc-5yec
Aliases: CVE-2025-0167 |
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. |
Affected by 4 other vulnerabilities. |
|
VCID-9atx-frk5-yfan
Aliases: CVE-2025-10148 |
Affected by 0 other vulnerabilities. |
|
|
VCID-9yvj-e9uf-9fcv
Aliases: CVE-2024-2004 |
When a protocol selection parameter option disables all protocols without adding any then the default set of protocols would remain in the allowed set due to an error in the logic for removing protocols. The below command would perform a request to curl.se with a plaintext protocol which has been explicitly disabled. curl --proto -all,-http http://curl.se The flaw is only present if the set of selected protocols disables the entire set of available protocols, in itself a command with no practical use and therefore unlikely to be encountered in real situations. The curl security team has thus assessed this to be low severity bug. |
Affected by 10 other vulnerabilities. |
|
VCID-acrb-uq4p-8bef
Aliases: CVE-2024-2398 |
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 headers and instead leaks the memory. Further, this error condition fails silently and is therefore not easily detected by an application. |
Affected by 10 other vulnerabilities. |
|
VCID-c3h6-xytf-sye2
Aliases: CVE-2025-5025 |
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, users could unwittingly connect to an impostor server without noticing. |
Affected by 3 other vulnerabilities. |
|
VCID-fpgg-hvnw-juea
Aliases: CVE-2024-0853 |
curl inadvertently kept the SSL session ID for connections in its cache even when the verify status (*OCSP stapling*) test failed. A subsequent transfer to the same hostname could then succeed if the session ID cache was still fresh, which then skipped the verify status check. |
Affected by 14 other vulnerabilities. |
|
VCID-k5f5-nr7b-n3ce
Aliases: CVE-2024-11053 |
When asked to both 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 an entry that matches the redirect target hostname but the entry either omits just the password or omits both login and password. |
Affected by 7 other vulnerabilities. |
|
VCID-k66x-9gtj-j7bp
Aliases: CVE-2024-9681 |
When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than otherwise intended. This affects curl using applications that enable HSTS and use URLs with the insecure `HTTP://` scheme and perform transfers with hosts like `x.example.com` as well as `example.com` where the first host is a subdomain of the second host. (The HSTS cache either needs to have been populated manually or there needs to have been previous HTTPS accesses done as the cache needs to have entries for the domains involved to trigger this problem.) When `x.example.com` responds with `Strict-Transport-Security:` headers, this bug can make the subdomain's expiry timeout *bleed over* and get set for the parent domain `example.com` in curl's HSTS cache. The result of a triggered bug is that HTTP accesses to `example.com` get converted to HTTPS for a different period of time than what was asked for by the origin server. If `example.com` for example stops supporting HTTPS at its expiry time, curl might then fail to access `http://example.com` until the (wrongly set) timeout expires. This bug can also expire the parent's entry *earlier*, thus making curl inadvertently switch back to insecure HTTP earlier than otherwise intended. |
Affected by 7 other vulnerabilities. |
|
VCID-s9w4-b85c-ffd6
Aliases: CVE-2025-9086 |
Affected by 0 other vulnerabilities. |
|
|
VCID-scmm-h2kh-p7f9
Aliases: CVE-2024-7264 |
libcurl's ASN1 parser code has the `GTime2str()` function, used for parsing an ASN.1 Generalized Time field. If given an syntactically incorrect field, the parser might end up using -1 for the length of the *time fraction*, leading to a `strlen()` getting performed on a pointer to a heap buffer area that is not (purposely) null terminated. This flaw most likely leads to a crash, but can also lead to heap contents getting returned to the application when [CURLINFO_CERTINFO](https://curl.se/libcurl/c/CURLINFO_CERTINFO.html) is used. |
Affected by 9 other vulnerabilities. |
|
VCID-vyre-1jrv-rqea
Aliases: CVE-2025-0725 |
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. |
Affected by 4 other vulnerabilities. |
|
VCID-zvxa-mr6f-x3bj
Aliases: CVE-2024-2466 |
libcurl did not check the server certificate of TLS connections done to a host specified as an IP address, when built to use mbedTLS. libcurl would wrongly avoid using the set hostname function when the specified hostname was given as an IP address, therefore completely skipping the certificate check. This affects all uses of TLS protocols (HTTPS, FTPS, IMAPS, POPS3, SMTPS, etc). |
Affected by 10 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-ntbe-4v75-c3c1 | When saving HSTS data to an excessively long file name, curl could end up removing all contents, making subsequent requests using that file unaware of the HSTS status they should otherwise use. |
CVE-2023-46219
|
| VCID-rpcy-cmfw-8ydm | 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 by exploiting a mixed case flaw in curl's function that verifies a given cookie domain against the Public Suffix List (PSL). For example a cookie could be set with `domain=co.UK` when the URL used a lower case hostname `curl.co.uk`, even though `co.uk` is listed as a PSL domain. |
CVE-2023-46218
|
| Date | Actor | Action | Vulnerability | Source | VulnerableCode Version |
|---|---|---|---|---|---|
| 2025-09-10T11:50:42.520468+00:00 | Curl Importer | Affected by | VCID-s9w4-b85c-ffd6 | https://curl.se/docs/CVE-2025-9086.json | 37.0.0 |
| 2025-09-10T11:50:41.918820+00:00 | Curl Importer | Affected by | VCID-9atx-frk5-yfan | https://curl.se/docs/CVE-2025-10148.json | 37.0.0 |
| 2025-07-31T09:34:12.052253+00:00 | Curl Importer | Fixing | VCID-rpcy-cmfw-8ydm | https://curl.se/docs/CVE-2023-46218.json | 37.0.0 |
| 2025-07-31T09:34:11.639205+00:00 | Curl Importer | Fixing | VCID-ntbe-4v75-c3c1 | https://curl.se/docs/CVE-2023-46219.json | 37.0.0 |
| 2025-07-31T09:34:11.527839+00:00 | Curl Importer | Affected by | VCID-fpgg-hvnw-juea | https://curl.se/docs/CVE-2024-0853.json | 37.0.0 |
| 2025-07-31T09:34:11.493290+00:00 | Curl Importer | Affected by | VCID-9yvj-e9uf-9fcv | https://curl.se/docs/CVE-2024-2004.json | 37.0.0 |
| 2025-07-31T09:34:11.350613+00:00 | Curl Importer | Affected by | VCID-acrb-uq4p-8bef | https://curl.se/docs/CVE-2024-2398.json | 37.0.0 |
| 2025-07-31T09:34:10.925979+00:00 | Curl Importer | Affected by | VCID-zvxa-mr6f-x3bj | https://curl.se/docs/CVE-2024-2466.json | 37.0.0 |
| 2025-07-31T09:34:10.794948+00:00 | Curl Importer | Affected by | VCID-scmm-h2kh-p7f9 | https://curl.se/docs/CVE-2024-7264.json | 37.0.0 |
| 2025-07-31T09:34:10.279221+00:00 | Curl Importer | Affected by | VCID-1ypr-54n1-27hn | https://curl.se/docs/CVE-2024-8096.json | 37.0.0 |
| 2025-07-31T09:34:09.802668+00:00 | Curl Importer | Affected by | VCID-k66x-9gtj-j7bp | https://curl.se/docs/CVE-2024-9681.json | 37.0.0 |
| 2025-07-31T09:34:09.581605+00:00 | Curl Importer | Affected by | VCID-k5f5-nr7b-n3ce | https://curl.se/docs/CVE-2024-11053.json | 37.0.0 |
| 2025-07-31T09:34:09.349113+00:00 | Curl Importer | Affected by | VCID-4g24-wxrc-5yec | https://curl.se/docs/CVE-2025-0167.json | 37.0.0 |
| 2025-07-31T09:34:09.084764+00:00 | Curl Importer | Affected by | VCID-vyre-1jrv-rqea | https://curl.se/docs/CVE-2025-0725.json | 37.0.0 |
| 2025-07-31T09:34:07.952044+00:00 | Curl Importer | Affected by | VCID-c3h6-xytf-sye2 | https://curl.se/docs/CVE-2025-5025.json | 37.0.0 |