RHSA-2026:34975CriticalCVSS 8.1

Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update

Published
July 2, 2026
Last Modified
August 17, 2026

🔗 CVE IDs covered (24)

CVE-2026-59868 →CVE-2026-11352 →CVE-2026-11586 →CVE-2026-11856 →CVE-2026-14684 →CVE-2026-14685 →CVE-2026-59870 →CVE-2026-8925 →CVE-2026-8926 →CVE-2026-8927 →CVE-2026-8932 →CVE-2026-9546 →CVE-2026-9547 →CVE-2026-11564 →CVE-2026-38969 →CVE-2026-8458 →CVE-2026-9080 →CVE-2026-12064 →CVE-2026-14683 →CVE-2026-14686 →CVE-2026-8286 →CVE-2026-8924 →CVE-2026-9079 →CVE-2026-15187 →

📋 Description

CVE-2026-8286 — curl: curl: Insecure connection establishment due to TLS configuration mismatch CVE-2026-8458 — curl: libcurl: Unauthorized connection reuse due to a logical error CVE-2026-8924 — curl: curl: Cookie injection via malicious HTTP server using super cookies CVE-2026-8925 — curl: curl: Double-free vulnerability in SASL authentication CVE-2026-8926 — curl: curl: Information disclosure via incorrect .netrc password lookup CVE-2026-8927 — curl: Information disclosure due to uncleared proxy authentication state CVE-2026-8932 — libcurl: libcurl: Security feature bypass due to improper mTLS connection reuse CVE-2026-9079 — libcurl: libcurl: Information disclosure due to failure to clear proxy authentication credentials CVE-2026-9080 — libcurl: libcurl: Use-after-free via curl_easy_pause() in CURLMOPT_SOCKETFUNCTION callback CVE-2026-9546 — libcurl: libcurl: Information disclosure due to persistent Referer header CVE-2026-9547 — curl: curl: Man-in-the-middle attack via SSH host key bypass CVE-2026-11352 — curl: libcurl: curl/libcurl: Remote denial of service via QUIC UDP receive function vulnerability CVE-2026-11564 — libcurl: libcurl: Certificate validation bypass due to incorrect connection reuse CVE-2026-11586 — curl: curl: Denial of Service via WebSocket PING flood CVE-2026-11856 — curl: curl: Information disclosure via incorrect Digest authentication header reuse CVE-2026-12064 — curl: curl: SSH host verification bypass when using schemeless URLs with SFTP/SCP CVE-2026-14683 — HdrHistogram: HdrHistogram: Denial of Service via uncontrolled memory allocation CVE-2026-14684 — org.hdrhistogram/HdrHistogram: HdrHistogram: HdrHistogram: Denial of Service via uncontrolled memory allocation in decodeFromByteBuffer CVE-2026-14685 — HdrHistogram: HdrHistogram: Local state issue via 'Count' argument manipulation CVE-2026-14686 — HdrHistogram: HdrHistogram: Data integrity impact due to incorrect comparison CVE-2026-15187 — enquirer: Enquirer: Prototype pollution vulnerability allows remote attackers to modify object attributes CVE-2026-38969 — webrick: rubygem-webrick: WEBrick: Request smuggling via re-parsing of Content-Length header CVE-2026-59868 — js-yaml: js-yaml: Denial of Service via quadratic CPU time parsing with merge keys CVE-2026-59870 — js-yaml: js-yaml: Denial of Service via crafted YAML ordered-map document

🎯 Affected products5

  • Red Hat Hardened Images
  • rust-main@aarch64 as a component of Red Hat Hardened Images
  • rust-main@noarch as a component of Red Hat Hardened Images
  • rust-main@src as a component of Red Hat Hardened Images
  • rust-main@x86_64 as a component of Red Hat Hardened Images

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: Do not use trailing-dot hostnames in URLs passed to curl. Trailing dots are uncommon and incompatible with TLS SNI. Upgrade to curl 8.21.0 to resolve Workaround: To mitigate this issue, applications utilizing libcurl should avoid reusing handles when switching between different proxy configurations. This operational control prevents the unintended leakage of `Proxy-Authorization` headers to incorrect proxies. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Correct usage of the library: Create a fresh handle for a different origin, or explicitly clear authentication-related state before reuse: ```c // req.A curl = curl_easy_init(); ... curl_easy_cleanup(curl); // req.B curl = curl_easy_init(); ... curl_easy_cleanup(curl); ``` Fixed in libcurl 8.21.0; affected range: 7.10.6 – 8.20.0 Workaround: To mitigate this issue, avoid using the `--proto-default sftp` or `--proto-default scp` options with schemeless URLs when invoking the `curl` command. Instead, explicitly specify the protocol in the URL (e.g., `sftp://host/path` or `scp://host/path`). Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Workaround: Do not expose WEBrick directly to untrusted network traffic. WEBrick is not designed for production use and should be replaced with a production-grade Ruby application server (e.g., Puma, Unicorn) behind a reverse proxy (e.g., nginx, Apache, HAProxy) that performs its own Content-Length validation and strips or rejects requests with conflicting transfer encoding headers. A patch is available: https://github.com/ruby/webrick/pull/199 Workaround: Upgrade to js-yaml 5.2.0 or later. Where an immediate upgrade is not possible, avoid parsing untrusted YAML documents that use merge keys ('<<'), or apply size and time limits when parsing untrusted YAML input. Workaround: Avoid using the YAML11_SCHEMA when parsing untrusted YAML input, or upgrade to js-yaml 5.2.1 or later. Applications using the default schema (CORE_SCHEMA) are not affected.

🔗 References (28)