Curl
Vulnerability activity for Curl: what is being exploited, what was published lately, and when the next patch release is due.
Last 30 days
- CVEs
- 0
- Critical (CVSS 9+)
- 0
- Exploited (CISA KEV)
- 0
- With exploit code
- 0
Last 90 days
- CVEs
- 0
- Critical (CVSS 9+)
- 0
- Exploited (CISA KEV)
- 0
- With exploit code
- 0
Last 365 days
- CVEs
- 10
- Critical (CVSS 9+)
- 3
- Exploited (CISA KEV)
- 0
- With exploit code
- 0
Exploited now
None of this vendor's CVEs are on CISA's known-exploited list.
Recent
- 9.8CriticalJul 3, 2026curlCVE-2026-9079libcurl had a flaw that when instructed to clear proxy authentication credentials which made it not do so, leaving the old credentials around to get used for subsequent transfers that should not know nor use them.1.1% likely
- 7.5HighJul 3, 2026curl Auth bypass / access controlCVE-2026-8932libcurl 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. However, some TLS sett
- 9.1CriticalJul 3, 2026curl Auth bypass / access controlCVE-2026-8927When 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 transfer routed thro
- 9.8CriticalJul 3, 2026curl Auth bypass / access controlCVE-2026-11856Successfully 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 meant for `hostA`,
- 7.5HighMay 13, 2026curl Auth bypass / access controlCVE-2026-6276Using libcurl, when a custom `Host:` header is first set for an HTTP request and a second request is subsequently done using the same *easy handle* but without the custom `Host:` header set, the second request would use stale information and pass on cookies meant for the first host in the second req
- 6.5MediumMar 11, 2026curl Auth bypass / access controlCVE-2026-3784curl 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.
- 5.3MediumMar 11, 2026curlCVE-2026-3783When 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 eithe
- 5.3MediumJan 8, 2026curl Crypto / certificateCVE-2025-14819When 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 libcu
- 5.3MediumJan 8, 2026curlCVE-2025-14524When 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.
- 6.3MediumJan 8, 2026curlCVE-2025-14017When 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
Top products
- curl10 CVEs in the last year, 3 critical
Advisories
Official advisories from the last 90 days that name this vendor's CVEs.
- CISA · Oct 20, 2026Hitachi Energy RTU500 ProductCVE-2026-11856CVE-2026-6276CVE-2026-8927CVE-2026-8932CVE-2026-9079
- Apple · Aug 17, 2026iOS 18.7.10 and iPadOS 18.7.10CVE-2026-3783CVE-2026-3784
- Apple · Jul 27, 2026tvOS 26.6CVE-2026-3783CVE-2026-3784
- Apple · Jul 27, 2026iOS 26.6 and iPadOS 26.6CVE-2026-3783CVE-2026-3784
- Apple · Jul 27, 2026watchOS 26.6CVE-2026-3783CVE-2026-3784
- Apple · May 11, 2026macOS Tahoe 26.5CVE-2025-14017CVE-2025-14819
- Apple · Mar 24, 2026iOS 18.7.7 and iPadOS 18.7.7CVE-2025-14524
Counts cover CVEs and advisories Watch Floor tracks, by the date they became news. Updated every 10 minutes.