Skip to content
OpenAdvisories
Critical SUSE-SU-2026:5071-1 13 CVEs

Security update for curl

Published Nov 3, 2026 · Updated Nov 3, 2026

Summary

This update for curl fixes the following issues:

- CVE-2026-8932: incomplete mTLS config matching in conn reuse (bsc#1268414).
- CVE-2026-11856: cross-origin Digest auth state leak (bsc#1268426).
- CVE-2026-12064: proto-default skips SSH verification (bsc#1268427).
- CVE-2026-19931: Negotiate ambient user conn reuse (bsc#1277478).
- CVE-2026-86409: stale SigV4 headers sent unintended (bsc#1285031).
- CVE-2026-86410: redirect to SFTP or SCP bypasses host verification (bsc#1285030).
- CVE-2026-86414: leaking host credentials to HTTP proxy (bsc#1285026).
- CVE-2026-87864: IMAP APPEND plus CRLF conversion command injection (bsc#1285021).
- CVE-2026-92388: FTP wildcard write callback mixup (bsc#1285016).
- CVE-2026-92389: TFTP direction confusion (bsc#1285015).
- CVE-2026-92391: curl_mime_free stack overflow by recursion (bsc#1285013).
- CVE-2026-94266: password leak in CURLINFO_EFFECTIVE_URL (bsc#1285010).

Fixed packages 2

ReleasePackageFixed in
SUSE · SLES 12 SP5 Linux Enterprise Server 12 SP5-LTSS curl 8.0.1-11.134.1
SUSE · SLES 12 SP5 Linux Enterprise Server LTSS Extended Security 12 SP5 curl 8.0.1-11.134.1

Vulnerabilities 13

  • 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

    Negotiate ambient user conn reuse

    A flaw in libcurl makes it wrongly reuse an HTTP connection setup for a given hostname using Negotiate authentication, when the initial request is done using empty credentials. This can make user B's request get sent over user A's previously authenticated con…

  • Critical 9.1

    leaking host credentials to HTTP proxy

    An HTTP proxy can trick libcurl into sending the origin's credentials (Basic password, or a Negotiate/Kerberos ticket) to the proxy itself, by answering the `CONNECT` tunnel request with 401 `WWW-Authenticate:` instead of the expected 407 `Proxy-Authenticate:…

  • Critical 9.1

    FTP wildcard write callback mixup

    When an FTP wildcard `LIST` operation fails, libcurl omits the restoration path meant for successful listings, leaving the write callback set to the internal listing parser and the write callback data pointing directly to the easy handle. Subsequent reuse of …

  • High 8.1

    stale SigV4 headers sent unintended

    Setting `CURLOPT_AWS_SIGV4` to NULL but does not disable SigV4 authentication, contrary to expectations and documentation. A subsequent transfer on the same handle still sends an `Authorization: AWS4-HMAC-SHA256` header to whatever URL isset next, leaking sta…

  • High 8.1

    redirect to SFTP or SCP bypasses host verification

    A flaw in the curl command line tool's logic makes it only set SSH host verification options when interacting directly using SFTP or SCP, and not as a result of following a redirect.

  • High 8.1

    IMAP APPEND plus CRLF conversion command injection

    Enabling `CURLOPT_CRLF` causes curl to advertise the raw input byte count in the `IMAP APPEND {N}` literal while transmitting line-ending expanded data. The server reads only $N$ bytes for the payload, causing the remaining overflow bytes to be interpreted an…

  • High 8.1

    TFTP direction confusion

    libcurl's TFTP state machine fails to validate state transitions against the requested transfer direction, accepting opening server responses for both reads and writes interchangeably. A malicious TFTP server can respond to a download request in a way that fo…

  • 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

    curl_mime_free stack overflow by recursion

    A deeply nested multipart MIME structure constructed via the public API causes a stack overflow in libcurl during normal cleanup operations. An excessive recursion depth within `curl_mime_free` leads to unbounded stack frame allocation during structure traver…

  • High 7.5

    password leak in CURLINFO_EFFECTIVE_URL

    libcurl could accidentally return a URL for `curl_easy_getinfo()`'s `CURLINFO_EFFECTIVE_URL` option containing credentials, even though neither the URL provided to libcurl nor the redirected URL did.

  • 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/1268414
  • report
    https://bugzilla.suse.com/1268426
  • report
    https://bugzilla.suse.com/1268427
  • report
    https://bugzilla.suse.com/1277478
  • report
    https://bugzilla.suse.com/1285010
  • report
    https://bugzilla.suse.com/1285013
  • report
    https://bugzilla.suse.com/1285015
  • report
    https://bugzilla.suse.com/1285016
  • report
    https://bugzilla.suse.com/1285021
  • report
    https://bugzilla.suse.com/1285026
  • report
    https://bugzilla.suse.com/1285030
  • report
    https://bugzilla.suse.com/1285031
  • 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-19931
  • web
    https://www.suse.com/security/cve/CVE-2026-8458
  • web
    https://www.suse.com/security/cve/CVE-2026-86409
  • web
    https://www.suse.com/security/cve/CVE-2026-86410
  • web
    https://www.suse.com/security/cve/CVE-2026-86414
  • web
    https://www.suse.com/security/cve/CVE-2026-87864
  • web
    https://www.suse.com/security/cve/CVE-2026-8932
  • web
    https://www.suse.com/security/cve/CVE-2026-92388
  • web
    https://www.suse.com/security/cve/CVE-2026-92389
  • web
    https://www.suse.com/security/cve/CVE-2026-92391
  • web
    https://www.suse.com/security/cve/CVE-2026-94266