Skip to content
OpenAdvisories
High RHSA-2026:55450 7 CVEs

Red Hat Security Advisory: curl security update

Published Aug 17, 2026 · Updated Oct 16, 2026

Fixed packages 8

ReleasePackageFixed in
Red Hat · RHEL 10 enterprise_linux:10.2 curl 0:8.12.1-4.el10_2.3
Red Hat · RHEL 10 enterprise_linux:10.2 curl-debuginfo 0:8.12.1-4.el10_2.3
Red Hat · RHEL 10 enterprise_linux:10.2 curl-debugsource 0:8.12.1-4.el10_2.3
Red Hat · RHEL 10 enterprise_linux:10.2 libcurl 0:8.12.1-4.el10_2.3
Red Hat · RHEL 10 enterprise_linux:10.2 libcurl-debuginfo 0:8.12.1-4.el10_2.3
Red Hat · RHEL 10 enterprise_linux:10.2 libcurl-devel 0:8.12.1-4.el10_2.3
Red Hat · RHEL 10 enterprise_linux:10.2 libcurl-minimal 0:8.12.1-4.el10_2.3
Red Hat · RHEL 10 enterprise_linux:10.2 libcurl-minimal-debuginfo 0:8.12.1-4.el10_2.3

Vulnerabilities 7

  • High 8.1

    wrong STARTTLS connection reuse

    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.

  • High 7.5

    proto-default skips SSH verification

    When a user invokes curl using a schemeless URL combined with `--proto-default` sftp (or scp), a disconnect occurs between the tool layer and libcurl. The tool layer incorrectly infers the URL scheme, which erroneously bypasses the initialization of critical …

  • High 7.4

    SSH improper host validation

    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…

  • Medium 6.5

    bad reuse of HTTP Negotiate connection

    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 …

  • Medium 6.5

    wrong proxy connection reuse with credentials

    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.

  • Medium 5.3

    OpenSSL partial chain store policy bypass

    When 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 wishe…

  • Medium 5.3

    token leak with redirect and netrc

    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 informa…

References

  • article
    https://access.redhat.com/security/updates/classification/#important
  • report
    https://bugzilla.redhat.com/show_bug.cgi?id=2426408
  • report
    https://bugzilla.redhat.com/show_bug.cgi?id=2446448
  • report
    https://bugzilla.redhat.com/show_bug.cgi?id=2446449
  • report
    https://bugzilla.redhat.com/show_bug.cgi?id=2446450
  • report
    https://bugzilla.redhat.com/show_bug.cgi?id=2496758
  • report
    https://bugzilla.redhat.com/show_bug.cgi?id=2496763
  • report
    https://bugzilla.redhat.com/show_bug.cgi?id=2496768
  • advisory
    https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_55450.json
  • report
    https://access.redhat.com/security/cve/CVE-2025-14819
  • advisory
    https://www.cve.org/CVERecord?id=CVE-2025-14819
  • advisory
    https://nvd.nist.gov/vuln/detail/CVE-2025-14819
  • article
    https://curl.se/docs/CVE-2025-14819.html
  • report
    https://access.redhat.com/security/cve/CVE-2026-1965
  • advisory
    https://www.cve.org/CVERecord?id=CVE-2026-1965
  • advisory
    https://nvd.nist.gov/vuln/detail/CVE-2026-1965
  • article
    https://curl.se/docs/CVE-2026-1965.html
  • article
    https://curl.se/docs/CVE-2026-1965.json
  • report
    https://access.redhat.com/security/cve/CVE-2026-3783
  • advisory
    https://www.cve.org/CVERecord?id=CVE-2026-3783
  • advisory
    https://nvd.nist.gov/vuln/detail/CVE-2026-3783
  • article
    http://www.openwall.com/lists/oss-security/2026/03/11/2
  • article
    https://curl.se/docs/CVE-2026-3783.html
  • article
    https://curl.se/docs/CVE-2026-3783.json
  • article
    https://hackerone.com/reports/3583983
  • report
    https://access.redhat.com/security/cve/CVE-2026-3784
  • advisory
    https://www.cve.org/CVERecord?id=CVE-2026-3784
  • advisory
    https://nvd.nist.gov/vuln/detail/CVE-2026-3784
  • article
    http://www.openwall.com/lists/oss-security/2026/03/11/3
  • article
    https://curl.se/docs/CVE-2026-3784.html
  • article
    https://curl.se/docs/CVE-2026-3784.json
  • article
    https://hackerone.com/reports/3584903
  • report
    https://access.redhat.com/security/cve/CVE-2026-8286
  • advisory
    https://www.cve.org/CVERecord?id=CVE-2026-8286
  • advisory
    https://nvd.nist.gov/vuln/detail/CVE-2026-8286
  • article
    https://curl.se/docs/CVE-2026-8286.html
  • article
    https://curl.se/docs/CVE-2026-8286.json
  • article
    https://hackerone.com/reports/3718195
  • report
    https://access.redhat.com/security/cve/CVE-2026-9547