VYPR

Curl

by Curl

Source repositories

CVEs (211)

  • CVE-2003-1605HigAug 23, 2018
    risk 0.42cvss 7.5epss 0.02

    curl 7.x before 7.10.7 sends CONNECT proxy credentials to the remote server.

  • CVE-2016-9594MedApr 23, 2018
    risk 0.42cvss 6.5epss 0.02

    curl before version 7.52.1 is vulnerable to an uninitialized random in libcurl's internal function that returns a good 32bit random value. Having a weak or virtually non-existent random value makes the operations that use it vulnerable.

  • CVE-2018-1000121HigMar 14, 2018
    risk 0.42cvss 7.5epss 0.09

    A NULL pointer dereference exists in curl 7.21.0 to and including curl 7.58.0 in the LDAP code that allows an attacker to cause a denial of service

  • CVE-2026-13608HigSep 6, 2026
    risk 0.41cvss 7.4epss 0.01

    A flaw in the libcurl SASL negotiation for LDAP authentication allows an incomplete handshake sequence to be misinterpreted as a successful cryptographic verification. An attacker executing a Man-in-the-Middle (MITM) attack can inject a premature or shortcut response that…

  • CVE-2026-9547HigJul 3, 2026
    risk 0.41cvss 7.4epss 0.00

    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…

  • CVE-2025-0725HigFeb 5, 2025
    risk 0.41cvss 7.3epss 0.02

    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.

  • CVE-2016-0755HigJan 29, 2016
    risk 0.41cvss 7.3epss 0.09

    The ConnectionExists function in lib/url.c in libcurl before 7.47.0 does not properly re-use NTLM-authenticated proxy connections, which might allow remote attackers to authenticate as other users via a request, a similar issue to CVE-2014-0015.

  • CVE-2026-9080HigJul 3, 2026
    risk 0.40cvss 7.3epss 0.00

    Calling `curl_easy_pause()` within the event-based `CURLMOPT_SOCKETFUNCTION` callback triggers a use-after-free vulnerability, where libcurl attempts to store a flag using a dangling struct pointer immediately after that pointer's memory has been freed.

  • CVE-2025-0665HigFeb 5, 2025
    risk 0.39cvss 7.0epss 0.01

    libcurl would wrongly close the same eventfd file descriptor twice when taking down a connection channel after having completed a threaded name resolve.

  • CVE-2023-28320MedMay 26, 2023
    risk 0.39cvss 5.9epss 0.03

    A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different backends for resolving host names, selected at build time. If it is built to use the synchronous resolver, it allows name resolves to time-out slow operations using `alarm()`…

  • CVE-2016-9586MedApr 23, 2018
    risk 0.39cvss 5.9epss 0.05

    curl before version 7.52.0 is vulnerable to a buffer overflow when doing a large floating point output in libcurl's implementation of the printf() functions. If there are any application that accepts a format string from the outside without necessary input filtering, it could…

  • CVE-2025-13034MedJan 8, 2026
    risk 0.38cvss 5.9epss 0.00

    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 connection without…

  • CVE-2023-28321MedMay 26, 2023
    risk 0.38cvss 5.9epss 0.02

    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…

  • CVE-2022-32206MedJul 7, 2022
    risk 0.38cvss 6.5epss 0.36

    curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms. The number of acceptable "links" in this "decompression chain" was unbounded, allowing a malicious server to…

  • CVE-2024-7264MedJul 31, 2024
    risk 0.37cvss 6.5epss 0.20

    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…

  • CVE-2022-27776MedJun 2, 2022
    risk 0.36cvss 6.5epss 0.04

    A insufficiently protected credentials vulnerability in fixed in curl 7.83.0 might leak authentication or cookie header data on HTTP redirects to the same host but another port number.

  • CVE-2021-22922MedAug 5, 2021
    risk 0.36cvss 6.5epss 0.04

    When curl is instructed to download content using the metalink feature, thecontents is verified against a hash provided in the metalink XML file.The metalink XML file points out to the client how to get the same contentfrom a set of different URLs, potentially hosted by…

  • CVE-2026-8458MedJul 3, 2026
    risk 0.35cvss 6.5epss 0.00

    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…

  • CVE-2026-5545MedMay 13, 2026
    risk 0.35cvss 6.5epss 0.00

    libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) request after a Negotiate-authenticated one, when both use the same host. libcurl features a pool of recent connections so that subsequent requests can reuse an existing…

  • CVE-2026-3784MedMar 11, 2026
    risk 0.35cvss 6.5epss 0.00

    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.

Page 6 of 11