curl vulnerabilities and fixes

CVEs that mention curl, ranked by priority. 32 tracked.

curl has 32 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 14. Most recent: 2026-10-20. Highest priority: CVE-2023-27534 (score 57/100).

• CVE-2023-27534 HIGH 8.8 UPGRADE MITIGATE A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde (~) character to be
• CVE-2023-28319 HIGH 7.5 UPGRADE UPGRADE A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH ser
• CVE-2023-27535 MEDIUM 5.9 UPGRADE MITIGATE An authentication bypass vulnerability exists in libcurl <8.0.0 in the FTP connection reuse feature that can r
• CVE-2023-27536 MEDIUM 5.9 UPGRADE MITIGATE An authentication bypass vulnerability exists libcurl <8.0.0 in the connection reuse feature which can reuse p
• CVE-2023-28321 MEDIUM 5.9 UPGRADE MITIGATE An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of wil
• CVE-2022-43552 MEDIUM 5.9 UPGRADE UPGRADE A use after free vulnerability exists in curl <7.87.0
• CVE-2023-23916 MEDIUM 6.5 UPGRADE MITIGATE An allocation of resources without limits or throttling vulnerability exists in curl <v7.88.0 based on the "ch
• CVE-2023-28320 MEDIUM 5.9 UPGRADE UPGRADE A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different backend
• CVE-2023-27537 MEDIUM 5.9 DOWNGRADE MITIGATE A double free vulnerability exists in libcurl <8.0.0 when sharing HSTS data between separate "handles"
• CVE-2023-28322 LOW 3.7 UPGRADE MITIGATE An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might err
• CVE-2023-23915 MEDIUM 6.5 UPGRADE MITIGATE A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS
• CVE-2026-91766 MEDIUM 5.9 UPGRADE When the http:// stream wrapper follows a redirect it forwards the user-supplied Authorization, Cookie and Pro
• CVE-2023-23599 MEDIUM 6.5 UPGRADE UPGRADE When copying a network request from the developer tools panel as a curl command the output was not being prope
• CVE-2025-11713 HIGH 8.1 UPGRADE UPGRADE Insufficient escaping in the “Copy as cURL” feature could have been used to trick a user into executing unexpe
• CVE-2026-86413 HIGH n/a When using an *ambient user* in a first transfer doing Negotiate authentication and asked to follow redirects,
• CVE-2026-92387 HIGH n/a By permanently omitting the final control-response line, a malicious FTP, IMAP, POP3, or SMTP server can explo
• CVE-2026-94265 HIGH n/a When processing an HTTP redirect to a URL containing userinfo (a `username:password` component), curl might er
• CVE-2026-86410 HIGH n/a A flaw in the curl command line tool's logic makes it only set SSH host verification options when interacting
• CVE-2026-86412 HIGH n/a A remote HTTP server can set a cookie that curl accepts and writes to a Netscape cookie jar but cannot reload
• CVE-2026-86414 HIGH n/a An HTTP proxy can trick libcurl into sending the origin's credentials (Basic password, or a Negotiate/Kerberos
• CVE-2026-87862 HIGH n/a Importing a `includeSubDomains` parent HSTS entry before a longer-lived child entry, silently drops the child
• CVE-2026-87865 HIGH n/a When libcurl uses libssh2 with a hashed `known_hosts` file, an unrelated initial entry can cause host key vali
• CVE-2026-92386 HIGH n/a When writing a long cookie name and value to a Netscape cookie jar, a remote HTTP server can make `curl` write
• CVE-2026-92388 HIGH n/a When an FTP wildcard `LIST` operation fails, libcurl omits the restoration path meant for successful listings,
• CVE-2026-92389 HIGH n/a libcurl's TFTP state machine fails to validate state transitions against the requested transfer direction, acc
• CVE-2026-92390 HIGH n/a When invoked with `--remote-header-name` (`-J`), curl fails to preserve its documented anti-clobbering protect
• CVE-2026-92391 HIGH n/a A deeply nested multipart MIME structure constructed via the public API causes a stack overflow in libcurl dur
• CVE-2026-94266 HIGH n/a libcurl could accidentally return a URL for `curl_easy_getinfo()`'s `CURLINFO_EFFECTIVE_URL` option containing
• CVE-2026-107928 HIGH n/a When curl is built with GnuTLS, a malicious WebSocket server can make curl send memory past its send buffer
• CVE-2026-87864 HIGH n/a Enabling `CURLOPT_CRLF` causes curl to advertise the raw input byte count in the `IMAP APPEND {N}` literal whi
• CVE-2026-86415 HIGH n/a libcurl's connection cache match function never considers the automatic client certificate option, so a cached
• CVE-2026-87866 HIGH n/a When built with wolfSSL, curl can successfully validate a pinned public key hash against a key the TLS peer do

FAQ

How do I fix curl vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is curl being exploited right now?

None of the tracked curl CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which curl CVE should I patch first?

CVE-2023-27534 currently ranks highest (57/100): A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde (~) character to be .

← Back to latest CVEs