CVE-2026-92392

During an upload, curl mishandles HTTP/2 RST_STREAM received from the server (with reason HTTP_1_1_REQUIRED or REFUSED_STREAM) leading to a use after free of a struct Curl_easy object.

During an upload, curl mishandles HTTP/2 RST_STREAM received from the server (with reason HTTP_1_1_REQUIRED or REFUSED_STREAM) leading to a use after free of a struct Curl_easy object.

During an upload, curl mishandles HTTP/2 RST_STREAM received from the server (with reason HTTP_1_1_REQUIRED or REFUSED_STREAM) leading to a use after free of a struct Curl_easy object.

During an upload, curl mishandles HTTP/2 RST_STREAM received from the server (with reason HTTP_1_1_REQUIRED or REFUSED_STREAM) leading to a use after free of a struct Curl_easy object.

During an upload, curl mishandles HTTP/2 RST_STREAM received from the server (with reason HTTP_1_1_REQUIRED or REFUSED_STREAM) leading to a use after free of a struct Curl_easy object.

During an upload, curl mishandles HTTP/2 RST_STREAM received from the server (with reason HTTP_1_1_REQUIRED or REFUSED_STREAM) leading to a use after free of a struct Curl_easy object.

curl 8.23.0 has been released. It fixes 24 CVEs since 8.22.0, listed at https://curl.se/docs/security.html Not all of theses CVEs affect Mageia. Of the ones fixed in 8.23.0, these are the ones that do: CVE-2026-86410: redirect to SFTP or SCP bypasses host verification CVE-2026-86412: server-set cookie erases cookie jar CVE-2026-86413: Negotiate credentials sent to redirected origin CVE-2026-86414: leaking host credentials to HTTP proxy CVE-2026-86415: auto client cert connection reuse mixup CVE-2026-87861: cross-origin reuse of a Negotiate connection CVE-2026-87862: HSTS cache import drops longer-lived child CVE-2026-87863: HSTS response erases persisted entries CVE-2026-92386: server-set cookie aborts cookie jar load CVE-2026-92387: never-ending loop via server response omission CVE-2026-92388: FTP wildcard write callback mixup CVE-2026-92389: TFTP direction confusion CVE-2026-92390: -J no-clobber guarantee bypassed with 103 early hints CVE-2026-92391: curl_mime_free stack overflow by recursion CVE-2026-92392: HTTP/2 upload Use-After-Free CVE-2026-94265: Authorization: Negotiate sent to foreign origin CVE-2026-94266: password leak in CURLINFO_EFFECTIVE_URL CVE-2026-107929: local interface connection reuse mixup There were also some CVE IDs released at the same time that were fixed earlier, in 8.22.0, but just announced now: CVE-2026-86409: stale SigV4 headers sent unintended CVE-2026-86411: FTP connection reuse inherits client-certificate CVE-2026-87864: IMAP APPEND plus CRLF conversion command injection Here are the CVEs fixed in 8.22.0, which wasn't released in mga10 and so are only getting fixed now: CVE-2026-13608: OpenLDAP SASL authentication bypass CVE-2026-18924: HTTP/2 server push UAF CVE-2026-19931: Negotiate ambient user conn reuse CVE-2026-80229: OpenSSL provider use-after-free CVE-2026-80230: OpenSSL pinning bypass CVE-2026-80255: secure cookie attribute bypass with tab CVE-2026-82209: domain-scoped PSL domain cookie

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

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-18924: HTTP/2 server push UAF (bsc#1277477).
• CVE-2026-19931: Negotiate ambient user conn reuse (bsc#1277478).
• CVE-2026-80255: secure cookie attribute bypass with tab (bsc#1277482).
• CVE-2026-82209: domain-scoped PSL domain cookie (bsc#1278173).
• 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-87862: HSTS cache import drops longer-lived child (bsc#1285023).
• CVE-2026-87863: HSTS response erases persisted entries (bsc#1285022).
• CVE-2026-87864: IMAP APPEND plus CRLF conversion command injection (bsc#1285021).
• CVE-2026-92386: server-set cookie aborts cookie jar load (bsc#1285018).
• CVE-2026-92387: never-ending loop via server response omission (bsc#1285017).
• CVE-2026-92388: FTP wildcard write callback mixup (bsc#1285016).
• CVE-2026-92389: TFTP direction confusion (bsc#1285015).
• CVE-2026-92390: -J no-clobber guarantee bypassed with 103 early hints (bsc#1285014).
• CVE-2026-92391: curl_mime_free stack overflow by recursion (bsc#1285013).
• CVE-2026-92392: HTTP/2 upload Use-After-Free (bsc#1285012).
• CVE-2026-94266: password leak in CURLINFO_EFFECTIVE_URL (bsc#1285010).
• CVE-2026-107929: local interface connection reuse mixup (bsc#1285008).

This update for curl fixes the following issues:

• CVE-2026-8932: incomplete mTLS config matching in conn reuse (bsc#1268414).
• CVE-2026-9546: sending old referer (bsc#1268419).
• CVE-2026-11352: QUIC zero-length UDP datagrams busy-loop (bsc#1268423).
• CVE-2026-11564: Native CA trust persist (bsc#1268424).
• CVE-2026-11586: WS Auto-PONG memory exhaustion (bsc#1268425).
• CVE-2026-11856: cross-origin Digest auth state leak (bsc#1268426).
• CVE-2026-12064: proto-default skips SSH verification (bsc#1268427).
• CVE-2026-18924: HTTP/2 server push UAF (bsc#1277477).
• CVE-2026-19931: Negotiate ambient user conn reuse (bsc#1277478).
• CVE-2026-80255: secure cookie attribute bypass with tab (bsc#1277482).
• CVE-2026-82209: domain-scoped PSL domain cookie (bsc#1278173).
• 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-86411: FTP connection reuse inherits client-certificate (bsc#1285029).
• CVE-2026-86412: server-set cookie erases cookie jar (bsc#1285028).
• CVE-2026-86413: Negotiate credentials sent to redirected origin (bsc#1285027).
• CVE-2026-86414: leaking host credentials to HTTP proxy (bsc#1285026).
• CVE-2026-87861: cross-origin reuse of a Negotiate connection (bsc#1285024).
• CVE-2026-87862: HSTS cache import drops longer-lived child (bsc#1285023).
• CVE-2026-87863: HSTS response erases persisted entries (bsc#1285022).
• CVE-2026-87864: IMAP APPEND plus CRLF conversion command injection (bsc#1285021).
• CVE-2026-92386: server-set cookie aborts cookie jar load (bsc#1285018).
• CVE-2026-92387: never-ending loop via server response omission (bsc#1285017).
• CVE-2026-92388: FTP wildcard write callback mixup (bsc#1285016).
• CVE-2026-92389: TFTP direction confusion (bsc#1285015).
• CVE-2026-92390: -J no-clobber guarantee bypassed with 103 early hints (bsc#1285014).
• CVE-2026-92391: curl_mime_free stack overflow by recursion (bsc#1285013).
• CVE-2026-92392: HTTP/2 upload Use-After-Free (bsc#1285012).
• CVE-2026-94265: Authorization: Negotiate sent to foreign origin (bsc#1285011).
• CVE-2026-94266: password leak in CURLINFO_EFFECTIVE_URL (bsc#1285010).
• CVE-2026-107929: local interface connection reuse mixup (bsc#1285008).

Changes for curl:

• Updated curl to version 8.22.0. (jsc#PED-16984)

This update for curl fixes the following issues:

• CVE-2026-8932: incomplete mTLS config matching in conn reuse (bsc#1268414).
• CVE-2026-9546: sending old referer (bsc#1268419).
• CVE-2026-11352: QUIC zero-length UDP datagrams busy-loop (bsc#1268423).
• CVE-2026-11564: Native CA trust persist (bsc#1268424).
• CVE-2026-11586: WS Auto-PONG memory exhaustion (bsc#1268425).
• CVE-2026-11856: cross-origin Digest auth state leak (bsc#1268426).
• CVE-2026-12064: proto-default skips SSH verification (bsc#1268427).
• CVE-2026-18924: HTTP/2 server push UAF (bsc#1277477).
• CVE-2026-19931: Negotiate ambient user conn reuse (bsc#1277478).
• CVE-2026-80255: secure cookie attribute bypass with tab (bsc#1277482).
• CVE-2026-82209: domain-scoped PSL domain cookie (bsc#1278173).
• 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-86411: FTP connection reuse inherits client-certificate (bsc#1285029).
• CVE-2026-86412: server-set cookie erases cookie jar (bsc#1285028).
• CVE-2026-86413: Negotiate credentials sent to redirected origin (bsc#1285027).
• CVE-2026-86414: leaking host credentials to HTTP proxy (bsc#1285026).
• CVE-2026-87861: cross-origin reuse of a Negotiate connection (bsc#1285024).
• CVE-2026-87862: HSTS cache import drops longer-lived child (bsc#1285023).
• CVE-2026-87863: HSTS response erases persisted entries (bsc#1285022).
• CVE-2026-87864: IMAP APPEND plus CRLF conversion command injection (bsc#1285021).
• CVE-2026-92386: server-set cookie aborts cookie jar load (bsc#1285018).
• CVE-2026-92387: never-ending loop via server response omission (bsc#1285017).
• CVE-2026-92388: FTP wildcard write callback mixup (bsc#1285016).
• CVE-2026-92389: TFTP direction confusion (bsc#1285015).
• CVE-2026-92390: -J no-clobber guarantee bypassed with 103 early hints (bsc#1285014).
• CVE-2026-92391: curl_mime_free stack overflow by recursion (bsc#1285013).
• CVE-2026-92392: HTTP/2 upload Use-After-Free (bsc#1285012).
• CVE-2026-94265: Authorization: Negotiate sent to foreign origin (bsc#1285011).
• CVE-2026-94266: password leak in CURLINFO_EFFECTIVE_URL (bsc#1285010).
• CVE-2026-107929: local interface connection reuse mixup (bsc#1285008).

Changes for curl:

• Updated to version 8.22.0. (jsc#PED-16984)

It was discovered that curl, when built with GnuTLS support, had an out-of-bounds read in the WebSocket send path. An attacker could possibly use this issue to obtain sensitive information. (CVE-2026-107928)

Maksim discovered that curl did not correctly include the interface binding in connection reuse decisions when CURLOPT_INTERFACE was used. An attacker could possibly use this issue to cause connections to go out from an unintended source address. (CVE-2026-107929)

Stanislav Fort discovered that curl did not properly clear AWS SigV4 authentication state when CURLOPT_AWS_SIGV4 was set to NULL. An attacker could possibly use this issue to obtain sensitive information. (CVE-2026-86409)

Stanislav Fort discovered that the curl command line tool did not set SSH host verification options when following redirects to SFTP or SCP URLs. An attacker could possibly use this issue to perform machine-in-the-middle attacks. (CVE-2026-86410)

Stanislav Fort discovered that curl did not properly handle cookie jar entries that could not be reloaded. An attacker could possibly use this issue to cause a denial of service. (CVE-2026-86412)

Stanislav Fort discovered that an HTTP proxy could trick libcurl into sending credentials to the proxy itself by responding to a CONNECT request with an unexpected authentication challenge. An attacker could possibly use this issue to obtain sensitive information. (CVE-2026-86414)

Stanislav Fort discovered that curl did not correctly handle HSTS entries when an includeSubDomains parent entry was imported before a longer-lived child entry. An attacker could possibly use this issue to cause curl to use unencrypted HTTP connections. (CVE-2026-87862)

Stanislav Fort discovered that curl did not properly handle HSTS max-age values that exceeded calendar time structure bounds. An attacker could possibly use this issue to cause a denial of service or data loss. (CVE-2026-87863)

Stanislav Fort discovered that curl did not properly handle IMAP APPEND commands when CURLOPT_CRLF was enabled, allowing overflow bytes to be interpreted as pipelined commands. An authenticated attacker could possibly use this issue to inject arbitrary IMAP commands. (CVE-2026-87864)

Bobbeh Rhino discovered that libcurl, when used with libssh2 and a hashed known_hosts file, could misreport a host key mismatch as a missing key. An attacker could possibly use this issue to perform machine-in-the-middle attacks. (CVE-2026-87865)

Joshua Rogers discovered that curl did not properly handle long cookie entries written to a Netscape cookie jar. An attacker could possibly use this issue to cause a denial of service. (CVE-2026-92386)

Joshua Rogers discovered that a malicious FTP, IMAP, POP3, or SMTP server could cause libcurl to block indefinitely by omitting the final control-response line. An attacker could possibly use this issue to cause a denial of service. (CVE-2026-92387)

Joshua Rogers discovered that libcurl had a use-after-free vulnerability in the FTP wildcard matching code. An attacker could possibly use this issue to cause curl to crash, resulting in a denial of service, or execute arbitrary code. (CVE-2026-92388)

Joshua Rogers discovered that libcurl's TFTP state machine did not properly validate transfer directions, allowing a malicious server to force the client into transmit mode. An attacker could possibly use this issue to obtain sensitive information. (CVE-2026-92389)

Joshua Rogers discovered that curl did not properly enforce its file overwrite protection when using --remote-header-name in certain circumstances. An attacker could possibly use this issue to overwrite local files. (CVE-2026-92390)

Joshua Rogers discovered that curl had a stack overflow vulnerability when processing deeply nested MIME structures. An attacker could possibly use this issue to cause curl to crash, resulting in a denial of service. (CVE-2026-92391)

Joshua Rogers discovered that libcurl could expose credentials in the URL returned by…

USN-8927-1 fixed vulnerabilities in curl. This update provides the corresponding fixes for Ubuntu 26.10.

Original advisory details:

It was discovered that curl, when built with GnuTLS support, had an out-of-bounds read in the WebSocket send path. An attacker could possibly use this issue to obtain sensitive information. (CVE-2026-107928)

Maksim discovered that curl did not correctly include the interface binding in connection reuse decisions when CURLOPT_INTERFACE was used. An attacker could possibly use this issue to cause connections to go out from an unintended source address. (CVE-2026-107929)

Stanislav Fort discovered that curl did not properly clear AWS SigV4 authentication state when CURLOPT_AWS_SIGV4 was set to NULL. An attacker could possibly use this issue to obtain sensitive information. (CVE-2026-86409)

Stanislav Fort discovered that the curl command line tool did not set SSH host verification options when following redirects to SFTP or SCP URLs. An attacker could possibly use this issue to perform machine-in-the-middle attacks. (CVE-2026-86410)

Stanislav Fort discovered that curl did not properly handle cookie jar entries that could not be reloaded. An attacker could possibly use this issue to cause a denial of service. (CVE-2026-86412)

Stanislav Fort discovered that an HTTP proxy could trick libcurl into sending credentials to the proxy itself by responding to a CONNECT request with an unexpected authentication challenge. An attacker could possibly use this issue to obtain sensitive information. (CVE-2026-86414)

Stanislav Fort discovered that curl did not correctly handle HSTS entries when an includeSubDomains parent entry was imported before a longer-lived child entry. An attacker could possibly use this issue to cause curl to use unencrypted HTTP connections. (CVE-2026-87862)

Stanislav Fort discovered that curl did not properly handle HSTS max-age values that exceeded calendar time structure bounds. An attacker could possibly use this issue to cause a denial of service or data loss. (CVE-2026-87863)

Stanislav Fort discovered that curl did not properly handle IMAP APPEND commands when CURLOPT_CRLF was enabled, allowing overflow bytes to be interpreted as pipelined commands. An authenticated attacker could possibly use this issue to inject arbitrary IMAP commands. (CVE-2026-87864)

Bobbeh Rhino discovered that libcurl, when used with libssh2 and a hashed known_hosts file, could misreport a host key mismatch as a missing key. An attacker could possibly use this issue to perform machine-in-the-middle attacks. (CVE-2026-87865)

Joshua Rogers discovered that curl did not properly handle long cookie entries written to a Netscape cookie jar. An attacker could possibly use this issue to cause a denial of service. (CVE-2026-92386)

Joshua Rogers discovered that a malicious FTP, IMAP, POP3, or SMTP server could cause libcurl to block indefinitely by omitting the final control-response line. An attacker could possibly use this issue to cause a denial of service. (CVE-2026-92387)

Joshua Rogers discovered that libcurl had a use-after-free vulnerability in the FTP wildcard matching code. An attacker could possibly use this issue to cause curl to crash, resulting in a denial of service, or execute arbitrary code. (CVE-2026-92388)

Joshua Rogers discovered that libcurl's TFTP state machine did not properly validate transfer directions, allowing a malicious server to force the client into transmit mode. An attacker could possibly use this issue to obtain sensitive information. (CVE-2026-92389)

Joshua Rogers discovered that curl did not properly enforce its file overwrite protection when using --remote-header-name in certain circumstances. An attacker could possibly use this issue to overwrite local files. (CVE-2026-92390)

Joshua Rogers discovered that curl had a stack overflow vulnerability when processing deeply nested MIME structures. An attacker could…