Skip to content
OpenAdvisories
Critical openSUSE-SU-2026:21272-1 10 CVEs

Security update for curl

Published Jul 8, 2026 · Updated Jul 11, 2026

Summary

This update for curl fixes the following issues

- CVE-2026-8286: wrong STARTTLS connection reuse (bsc#1268402).
- CVE-2026-8458: wrong reuse for different services (bsc#1268407).
- CVE-2026-8924: traling dot domain super cookie (bsc#1268409).
- CVE-2026-8927: env-set cross-proxy Digest auth state leak (bsc#1268413).
- CVE-2026-9079: stale proxy password leak (bsc#1268415).
- CVE-2026-9080: UAF after pause in socket callback (bsc#1268416).
- CVE-2026-9545: exposing HTTP/3 early data (bsc#1268417).
- CVE-2026-9547: SSH improper host validation (bsc#1268420).
- CVE-2026-10536: HTTP/2 stream-dependency tree UAF (bsc#1268422).
- CVE-2026-12064: proto-default skips SSH verification (bsc#1268427).

Fixed packages 1

ReleasePackageFixed in
openSUSE · Leap 16.0 curl 8.14.1-160000.8.1

Vulnerabilities 10

  • 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

    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

    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

    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

    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

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

  • report
    https://bugzilla.suse.com/1268402
  • report
    https://bugzilla.suse.com/1268407
  • report
    https://bugzilla.suse.com/1268409
  • report
    https://bugzilla.suse.com/1268413
  • report
    https://bugzilla.suse.com/1268415
  • report
    https://bugzilla.suse.com/1268416
  • report
    https://bugzilla.suse.com/1268417
  • report
    https://bugzilla.suse.com/1268420
  • report
    https://bugzilla.suse.com/1268422
  • report
    https://bugzilla.suse.com/1268427
  • web
    https://www.suse.com/security/cve/CVE-2026-10536
  • 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-8927
  • 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-9547