Skip to content
OpenAdvisories
Critical openSUSE-SU-2026:11230-1 18 CVEs

curl-8.21.0-1.1 on GA media

Published Jul 9, 2026 · Updated Jul 10, 2026

Summary

These are all security issues fixed in the curl-8.21.0-1.1 package on the GA media of openSUSE Tumbleweed.

Fixed packages 1

ReleasePackageFixed in
openSUSE · Tumbleweed curl 8.21.0-1.1

Vulnerabilities 18

  • Critical 9.8

    HTTP/2 stream-dependency tree UAF

    A use-after-free vulnerability exists in libcurl when an application configures an HTTP/2 stream-dependency tree via `CURLOPT_STREAM_DEPENDS` or `CURLOPT_STREAM_DEPENDS_E`, subsequently invokes `curl_easy_reset()`, and finally terminates the handle with `curl…

  • Critical 9.8

    cross-origin Digest auth state leak

    Successfully 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 `Authori…

  • Critical 9.8

    SASL double-free

    The curl logic that works with SASL authentication could end up cleaning up the GSASL context *twice* without clearing the pointer in between, making it `free()` the same pointer twice.

  • Critical 9.8

    stale proxy password leak

    libcurl 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.

  • Critical 9.1

    Native CA trust persist

    libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. An easy handle that first uses default native CA trust can continue trusting the native platform store after the application swi…

  • Critical 9.1

    trailing dot domain super cookie

    A flaw in curl’s cookie parsing logic allows a malicious HTTP server to set "super cookies" that bypass the Public Suffix List check. This enables an attacker-controlled origin to inject cookies that curl subsequently scopes and transmits to unrelated third-p…

  • Critical 9.1

    password leak with netrc and user in URL

    When asking curl to use a `.netrc` file to find credentials and at the same time specifying a URL with a username (without a password), like `https://user@example.com/`, curl could wrongly get and use the password for *another* user set in the `.netrc` file f…

  • Critical 9.1

    env-set cross-proxy Digest auth state leak

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

  • 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

    QUIC zero-length UDP datagrams busy-loop

    An issue in curl’s QUIC UDP receive function allows a malicious HTTP/3 server to trigger a remote denial of service against a curl or libcurl client. Because the helper function discards zero-length UDP datagrams before counting them toward the per-call packe…

  • High 7.5

    WS Auto-PONG memory exhaustion

    By default, curl automatically responds to WebSocket PING frames. Because curl lacks an upper bound on memory allocation for unacknowledged frames, a malicious server can exhaust all available memory by flooding curl with rapid, sequential PING messages.

  • 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.5
    CVE-2026-8932 Public exploit

    incomplete mTLS config matching in conn reuse

    libcurl 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 m…

  • High 7.5

    exposing HTTP/3 early data

    In this scenario, libcurl first uses a proper HTTP/3 server for the initial transfers, and when it makes a second transfer to the same site it has been replaced by the attacker's impostor machine - without a valid certificate. When libcurl returns to the host…

  • High 7.5

    sending old referer

    A vulnerability in libcurl caused the HTTP `Referer:` header to persist even when explicitly cleared. While the documentation states that passing NULL to `CURLOPT_REFERER` suppresses the header, the option failed to clear the internal state. As a result, the …

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

  • High 7.3

    UAF after pause in socket callback

    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.

  • Medium 6.5

    wrong reuse for different services

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

References

  • web
    https://www.suse.com/security/cve/CVE-2026-10536
  • web
    https://www.suse.com/security/cve/CVE-2026-11352
  • web
    https://www.suse.com/security/cve/CVE-2026-11564
  • web
    https://www.suse.com/security/cve/CVE-2026-11586
  • web
    https://www.suse.com/security/cve/CVE-2026-11856
  • web
    https://www.suse.com/security/cve/CVE-2026-12064
  • web
    https://www.suse.com/security/cve/CVE-2026-8286
  • web
    https://www.suse.com/security/cve/CVE-2026-8458
  • web
    https://www.suse.com/security/cve/CVE-2026-8924
  • web
    https://www.suse.com/security/cve/CVE-2026-8925
  • web
    https://www.suse.com/security/cve/CVE-2026-8926
  • web
    https://www.suse.com/security/cve/CVE-2026-8927
  • web
    https://www.suse.com/security/cve/CVE-2026-8932
  • web
    https://www.suse.com/security/cve/CVE-2026-9079
  • web
    https://www.suse.com/security/cve/CVE-2026-9080
  • web
    https://www.suse.com/security/cve/CVE-2026-9545
  • web
    https://www.suse.com/security/cve/CVE-2026-9546
  • web
    https://www.suse.com/security/cve/CVE-2026-9547