RHSA-2026:67165HighCVSS 7.5

Red Hat Security Advisory: openssl security, bug fix, and enhancement update

Published
September 14, 2026
Last Modified
October 30, 2026

🔗 CVE IDs covered (10)

CVE-2026-14457 →CVE-2026-18798 →CVE-2026-63073 →CVE-2026-63076 →CVE-2026-75803 →CVE-2026-14456 →CVE-2026-54874 →CVE-2026-63072 →CVE-2026-63074 →CVE-2026-63075 →

📋 Description

CVE-2026-14456 — openssl: OpenSSL: Denial of Service via unbounded memory growth in QUIC server CVE-2026-14457 — openssl: RPK server signature algorithm selection can dereference a missing certificate CVE-2026-18798 — openssl: QUIC server may trigger double free when processing INITIAL packet CVE-2026-54874 — openssl: excessive memory use buffering DTLS records for a future epoch CVE-2026-63072 — openssl: heap buffer overflow in CMS key unwrapping CVE-2026-63073 — openssl: untrusted sender DN used as format string in CMP response validation CVE-2026-63074 — openssl: CMP indefinite cache growth of ExtraCerts CVE-2026-63075 — openssl: QUIC ACK-only packet retention can cause memory exhaustion CVE-2026-63076 — openssl: invalid pointer dereference in CMP server via crafted protectionAlg CVE-2026-75803 — openssl: openssl: AEAD forgeries possible with empty ciphertext in EVP_Cipher()

🎯 Affected products51

  • Red Hat Enterprise Linux AppStream (v. 9)
  • Red Hat Enterprise Linux BaseOS (v. 9)
  • openssl-1:3.5.8-1.el9_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • openssl-1:3.5.8-1.el9_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • openssl-1:3.5.8-1.el9_8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • openssl-1:3.5.8-1.el9_8.src as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • openssl-1:3.5.8-1.el9_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • openssl-debuginfo-1:3.5.8-1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • openssl-debuginfo-1:3.5.8-1.el9_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • openssl-debuginfo-1:3.5.8-1.el9_8.i686 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • openssl-debuginfo-1:3.5.8-1.el9_8.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • openssl-debuginfo-1:3.5.8-1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • openssl-debuginfo-1:3.5.8-1.el9_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • openssl-debuginfo-1:3.5.8-1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • openssl-debuginfo-1:3.5.8-1.el9_8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • openssl-debuginfo-1:3.5.8-1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • openssl-debuginfo-1:3.5.8-1.el9_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • openssl-debugsource-1:3.5.8-1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • openssl-debugsource-1:3.5.8-1.el9_8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • openssl-debugsource-1:3.5.8-1.el9_8.i686 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • openssl-debugsource-1:3.5.8-1.el9_8.i686 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • openssl-debugsource-1:3.5.8-1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • openssl-debugsource-1:3.5.8-1.el9_8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • openssl-debugsource-1:3.5.8-1.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • openssl-debugsource-1:3.5.8-1.el9_8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • openssl-debugsource-1:3.5.8-1.el9_8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • openssl-debugsource-1:3.5.8-1.el9_8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)
  • openssl-devel-1:3.5.8-1.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • openssl-devel-1:3.5.8-1.el9_8.i686 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • openssl-devel-1:3.5.8-1.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • +21 more not shown

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: Option 1: Rate-limit or Firewall Inbound QUIC (UDP 443) [Goal: Slow or block QUIC Initial packets before they reach the vulnerable listener.] A. Confirm QUIC Exposure - Check if any service is listening on UDP 443: ~~~ $ ss -ulnp | grep ':443' # or $ sudo lsof -iUDP:443 -n -P ~~~ Note: If no service is listening on UDP 443, this CVE does not apply (TCP 443 is unaffected). B. Restrict Access to UDP 443 ( Default-deny UDP 443 and allow only trusted networks:) ~~~ $ sudo firewall-cmd --permanent --remove-service=quic 2>/dev/null $ sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="10.0.0.0/8" port port="443" protocol="udp" accept' $ sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" port port="443" protocol="udp" drop' $ sudo firewall-cmd --reload ~~~ C. Verify - Confirm the restriction by testing from an external host (the connection should fail or be throttled): ~~~ $ nc -u -v YOUR_HOST 443 ~~~ Option 2: Disable QUIC Server If QUIC/HTTP3 is not required, remove the vulnerable code path entirely and use TLS/TCP instead. Recommended Mitigation Priority Priority : Action 1.Confirm UDP 443 QUIC listener exists and OpenSSL version is in affected range 2.Block or rate-limit UDP 443 at firewall/edge (immediate) 3.Disable QUIC/HTTP3 on the service if not needed 4.Upgrade OpenSSL to fixed release when available 5.Application owners: set SSL_VALUE_QUIC_MAX_PENDING_CONNS if default 256 is too high 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: To mitigate this ensure that all integrity check values present in messages are properly checked in accordance with the protocol specification before they are parsed and used. Applications must rigorously calculate the checksum and explicitly verify that the received integrity value matches the calculated one to prevent malicious data injection.

🔗 References (13)