Skip to main content
Mallory
← Back to News
open-source-dependency-vulnerabilitywidely-deployed-product-advisory

OpenSSL Fixes Five Low-Severity Flaws in QUIC, AES-GCM-SIV and CMS

Vulnerability Disclosure · 25 sources · Updated 6d ago · First seen Nov 10, 2026

OpenSSL Fixes Five Low-Severity Flaws in QUIC, AES-GCM-SIV and CMS

OpenSSL disclosed five Low-severity vulnerabilities affecting QUIC, AES-GCM-SIV and CMS encryption. The flaws can cause connection failures, denial of service, limited memory disclosure, or failures to authenticate additional data and bind authentication tags to initialization vectors. Fixes have been merged into the public repository, with releases scheduled for December 1, 2026. The QUIC and AES-GCM-SIV issues affect OpenSSL 4.1, 4.0 and 3.5 branches; the CMS issue also affects 3.0, 1.1.1 and 1.0.2 under the advisory’s stated conditions. OpenSSL says its FIPS modules are unaffected by all five issues.

One QUIC flaw, CVE-2026-88822, involves an incorrect buffer-length argument to getpeername() during automated peer detection on an already connected socket. This can leave part of the peer address uninitialized, particularly for IPv6, causing OpenSSL to send packets using an invalid destination address and potentially exposing stack data to passive network observers. The CMS flaw can trigger an infinite loop when encrypting to an attacker-controlled elliptic-curve certificate. Organizations should identify applications using the affected features and plan upgrades to 4.1.1, 4.0.4 or 3.5.10, as appropriate, once released; deployments on older CMS-affected branches should follow the branch-specific remediation in OpenSSL’s advisory.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

20 events · Jul 23, 2026 – Nov 11, 2026
  1. Reported Nov 11, 20266d ago

    Red Hat fixes OpenSSL QUIC connection-ID backlog denial of service

    Red Hat addressed CVE-2026-84784 in RHEL 9 and 10 through advisories RHSA-2026:98484 and RHSA-2026:98588. A malicious QUIC peer can flood NEW_CONNECTION_ID frames and withhold acknowledgments, exploiting premature connection-ID retirement to cause approximately 400 MB of memory allocation and potential denial of service.

    2543261 - (CVE-2026-84784) CVE-2026-84784 openssl: OpenSSL: Denial of Service via unbounded QUIC connection identifier backlog
  2. Reported Nov 11, 20266d ago

    Red Hat fixes OpenSSL QUIC traffic-amplification vulnerability

    Red Hat addressed CVE-2026-35191 in RHEL 9 and 10 through advisories RHSA-2026:98484 and RHSA-2026:98588, respectively. When client address validation is disabled, repeated counting of a datagram's length for each enclosed QUIC packet can let spoofing attackers exceed the server's three-times amplification limit and amplify DDoS traffic.

    2543257 - (CVE-2026-35191) CVE-2026-35191 openssl: openssl: Traffic amplification Denial of Service via QUIC packet over-accounting
  3. Reported Nov 11, 20266d ago

    Red Hat fixes OpenSSL QUIC connection flow-control denial of service

    Red Hat addressed CVE-2026-75804 in RHEL 9 and 10 through advisories RHSA-2026:98484 and RHSA-2026:98588, respectively. Missing connection-level flow-control enforcement lets a malicious QUIC peer force approximately 100 MB of heap allocation per connection by opening multiple streams and withholding each stream’s first byte.

    2543254 - (CVE-2026-75804) CVE-2026-75804 openssl: OpenSSL: Denial of Service via unenforced QUIC connection flow control
  4. Reported Nov 11, 20266d ago

    Red Hat fixes OpenSSL elliptic-curve timing leak enabling private-key recovery

    Red Hat addressed CVE-2026-54872 in RHEL 9 and 10 through RHSA-2026:98484 and RHSA-2026:98588, respectively. Non-constant-time scalar padding in generic elliptic-curve operations can expose ECDSA or SM2 nonce information across many signing-time measurements, potentially enabling private-key recovery; dedicated NIST curve implementations and the described FIPS modules are unaffected.

    2543250 - (CVE-2026-54872) CVE-2026-54872 openssl: OpenSSL: Private key recovery via timing side-channel in generic elliptic curve operations
  5. Reported Nov 11, 20266d ago

    Red Hat fixes OpenSSL QUIC stream-reassembly denial of service

    Red Hat addressed CVE-2026-42772 in RHEL 9 and 10 through advisories RHSA-2026:98484 and RHSA-2026:98588, respectively. A remote QUIC peer that completes the handshake can send protocol-compliant, out-of-order STREAM frames to trigger quadratic reassembly processing, potentially causing CPU exhaustion and denial of service with low attacker bandwidth.

    2543249 - (CVE-2026-42772) CVE-2026-42772 openssl: openssl: Denial of Service via inefficient QUIC stream reassembly
  6. Reported Nov 11, 20266d ago

    Red Hat fixes OpenSSL CMP revocation-response denial of service

    Red Hat addressed CVE-2026-75805 in RHEL 9 and 10 through RHSA-2026:98484 and RHSA-2026:98588, respectively. A crafted revocation response can crash CMP clients that request revocation using a PKCS#10 CSR; exploitation requires a malicious or compromised CMP server, or a man-in-the-middle possessing the message-protection secret.

    2543247 - (CVE-2026-75805) CVE-2026-75805 openssl: openssl: Denial of Service via crafted CMP certificate revocation response
  7. Reported Nov 11, 20266d ago

    Red Hat fixes OpenSSL QUIC packet-buffer retention denial of service

    Red Hat addressed CVE-2026-54873 in RHEL 9 and 10 through RHSA-2026:98484 and RHSA-2026:98588; crafted QUIC packets can cause disproportionate memory consumption by retaining entire packet buffers for stream data. The fix tracks per-stream memory overhead and begins copying stream data into stream buffers with the next received packet after overhead exceeds 64 kB.

    2543244 - (CVE-2026-54873) CVE-2026-54873 openssl: openssl: Denial of Service via excessive QUIC packet buffer retention
  8. Reported Nov 11, 20266d ago

    Red Hat fixes OpenSSL CRL distribution-point memory-exhaustion vulnerability

    Red Hat addressed CVE-2026-35189 in RHEL 9 and 10 through RHSA-2026:98484 and RHSA-2026:98588; crafted certificates totaling approximately 100 KiB can trigger hundreds of MiB of allocation during TLS handshakes, potentially exhausting client or server memory. The fix defers CRL distribution-point processing until needed, reducing prolonged memory retention.

    2543242 - (CVE-2026-35189) CVE-2026-35189 openssl: openssl: Denial of Service via excessive memory allocation in CRL distribution point processing
  9. Nov 11, 20266d ago

    Red Hat releases RHEL 10 OpenSSL update fixing 12 vulnerabilities

    Red Hat issued Moderate-rated advisory RHSA-2026:98588, providing OpenSSL 3.5.9-1.el10_3 for RHEL 10 across four architectures to address 12 vulnerabilities involving denial of service, information disclosure, and timing-based private-key recovery. The update also fixes silent fallback to the default provider when fips.so is missing in FIPS mode and an automatic-initialization failure involving threads.

    RHSA-2026:98588 - Security Advisory - Red Hat Customer Portal
  10. Nov 11, 20266d ago

    Red Hat releases RHEL 9 OpenSSL update fixing 12 vulnerabilities

    Red Hat issued Moderate-rated advisory RHSA-2026:98484, providing OpenSSL 3.5.9-1.el9_9 for RHEL 9 to address 12 vulnerabilities, including elliptic-curve and SM2 timing side channels, information disclosure, and multiple denial-of-service flaws. The update also fixes silent fallback to the default provider when fips.so is missing in FIPS mode and an automatic-initialization failure involving threads.

    RHSA-2026:98484 - Security Advisory - Red Hat Customer Portal
  11. Nov 10, 20267d ago

    OpenSSL discloses five Low-severity vulnerabilities and announces public fixes

    OpenSSL published details of all five QUIC, AES-GCM-SIV, and CMS vulnerabilities, rated each Low severity, and stated that fixes had been committed to its public repository. It identified 4.1.1, 4.0.4, and 3.5.10 as the forthcoming fixed releases, scheduled for December 1, 2026, and said its FIPS modules were unaffected.

    CVE Record: CVE-2026-88822
  12. Reported Oct 31, 202617d ago

    OpenSSL fixes zero-length AAD updates and stale AAD reuse in AES-GCM-SIV

    OpenSSL commit 159e1de makes zero-length AAD updates succeed without discarding accumulated AAD. It also clears stored AAD when a key or IV is supplied or after prior encryption or decryption, while preserving pending AAD during parameter-only adjustments.

    AES-GCM-SIV: no-op on zero-length update and clear stale AAD on reuse · openssl/openssl@159e1de · GitHub
  13. Reported Oct 28, 202620d ago

    OpenSSL adds fixed-length IV validation for AES-GCM-SIV

    OpenSSL commit 5108723 adds validation that rejects supplied AES-GCM-SIV IV lengths that differ from the context's fixed nonce length, as well as values that cannot be decoded. It also registers the AEAD IV-length parameter in the parameter decoder definition.

    Reject unsupported IV lengths for AES-GCM-SIV · openssl/openssl@5108723 · GitHub
  14. Oct 8, 20261mo ago

    Yinxi Liu reports CMS encryption infinite-loop vulnerability

    Yinxi Liu reported CVE-2026-107496, in which CMS encryption to an attacker-controlled EC recipient certificate with group order 1 causes key generation to retry indefinitely. The resulting loop consumes a CPU core until interrupted.

    [no-title]
  15. Sep 25, 20262mo ago

    Jonathan Bateman submits another report of AES-GCM-SIV AAD flaw

    Jonathan Bateman of Rochester Institute of Technology reported CVE-2026-88823, adding a third credited report of the AES-GCM-SIV AAD authentication and context-reinitialization issue.

    [no-title]
  16. Sep 19, 20262mo ago

    Billy Brumley reports AES-GCM-SIV IV-handling vulnerability

    Billy Brumley of Rochester Institute of Technology reported CVE-2026-95692 and developed its fix. Nonstandard IV lengths can cause a small heap out-of-bounds read or crash for short IVs, while truncation of longer IVs undermines IV commitment.

    [no-title]
  17. Sep 11, 20262mo ago

    Filipe Casal reports QUIC CRYPTO stream use-after-free

    Filipe Casal of Trail of Bits reported CVE-2026-95691 and developed its fix. A malicious QUIC server can use overlapping retransmitted CRYPTO frames to trigger a client heap-use-after-free read, potentially causing denial of service or revealing one allocator-adjacent byte.

    [no-title]
  18. Sep 6, 20262mo ago

    Bhargava Shastry independently reports AES-GCM-SIV AAD flaw

    Bhargava Shastry submitted an additional report of CVE-2026-88823, the AES-GCM-SIV flaw that can exclude intended AAD from authentication.

    [no-title]
  19. Aug 28, 20263mo ago

    Jaehun Lee reports QUIC peer-detection memory disclosure

    Jaehun Lee reported CVE-2026-88822, in which an undersized length passed to getpeername() leaves part of a QUIC peer address uninitialized. Using that address for outgoing packets can break connections and expose stack bytes to passive network observers.

    [no-title]
  20. Jul 23, 20264mo ago

    Jérémy Jean reports AES-GCM-SIV authentication flaw

    Jérémy Jean of ANSSI reported CVE-2026-88823 to OpenSSL. Empty incremental additional authenticated data (AAD) updates can discard earlier AAD from authentication, while context reinitialization can improperly retain AAD from a previous use.

    [no-title]
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.