OpenSSL August Security Update Fixes 9 DoS Vulnerabilities: QUIC Double-Free and CMS 8-Byte Heap Overflow
On 25 Aug 2026 the OpenSSL project shipped advisories fixing 9 vulnerabilities: 2 Moderate, 7 Low, hitting QUIC, DTLS, CMS, and CMP. Officially not RCE, but heap corruption, NULL deref, and uncontrolled memory use can crash public TLS terminators.
On 25 Aug 2026 the OpenSSL project shipped advisories fixing 9 vulnerabilities: 2 Moderate, 7 Low, affecting QUIC, DTLS, CMS, CMP, and related crypto stacks. Maintainers state none of these yield RCE. Heap corruption, NULL deref, and uncontrolled memory use can still crash internet-facing TLS terminators. Impact is high for CDN, gateway, mail, and VPN infrastructure. Branches covered: 4.0, 3.6, 3.5, 3.4, 3.0. Upgrade now.
Incident overview
Nine CVEs, all DoS-focused. Highest attention:
- CVE-2026-18798 (Moderate): QUIC receive-path double-free. A malformed INITIAL packet can crash a QUIC server.
- CVE-2026-63072 (Moderate): 8-byte heap out-of-bounds write during CMS AES-WRAP-PAD key unwrap. Triggerable via
CMS_decrypt(); process crash.
The seven Low bugs hit CMP ASN.1 parsing, DTLS session resumption, CMS format-string formatting, RPK parsing, and AEAD forged empty ciphertext. OpenSSL says none are RCE. An attacker can still force process exit or unbounded resource use.
- Affected: OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0; 1.1.1 and 1.0.2 only on specific code paths
- Fixed in: 4.0.2 / 3.6.4 / 3.5.8 / 3.4.7 / 3.0.22
- Disclosure: CVE-Bund WID-SEC-2026-0995; OpenSSL advisories, redistributed by distros
Technical details
CVE-2026-18798 QUIC double-free
Bug sits in the QUIC receive path:
port_default_packet_handler() -> create QRX object -> pass to port_bind_channel()
if dest connection ID length < 8 bytes -> port_bind_channel() free(QRX) fails
upper-layer error handler free()s the same QRX again -> double free
A crafted INITIAL packet with connection ID shorter than 8 bytes crashes the QUIC server process or corrupts the heap on most glibc setups. Path is reachable in the QUIC stack. Maintainers say turning it into code execution is extremely hard.
CVE-2026-63072 CMS heap OOB write
CMS (Cryptographic Message Syntax) AES-WRAP-PAD unwrap writes 8 bytes past the allocated buffer if the attacker tampers with OID bytes. Reachable through the public CMS_decrypt() API. Default-on for mail signature verify, S/MIME gateways, CA cert parsing.
Other Low CVEs
- CVE-2026-63073: CMP sender name passed straight into a format-string function; attacker-controlled format string
- CVE-2026-63076: CMP password-based MAC (PBM) check NULL-derefs after ASN.1 parse failure; remote CMP server crash
- CVE-2026-28386~28390, 31789/31790: small triggerable DoS in DTLS, AEAD, RPK modules
Impact assessment
OpenSSL underpins HTTPS, QUIC, S/MIME, VPN, and most internet crypto. A DoS-only bug still amplifies cheaply on CDNs, TLS gateways, mail relays, hardware load balancers, and IoT endpoints. No botnet required — one reachable port can pin the server down:
- QUIC path: CDN / API gateway UDP 443 unavailable
- CMS path: mail gateway or cert-issuance service crashes after one ciphertext exchange
- CMP path: RA/CA issuance automation down
- AEAD flaw: forged empty ciphertext bypasses integrity checks on gateways that trust OpenSSL verify logic
Remediation
- Upgrade now: 4.0.2, 3.6.4, 3.5.8, 3.4.7, or 3.0.22 per branch. Rebuild every binary statically linked to OpenSSL
- Shrink protocol exposure during the patch window: disable QUIC and CMP endpoints; leave DTLS and TLS 1.2/1.3 only
- Config mitigation: on NGINX/HAProxy/Envoy, enforce QUIC INITIAL connection-ID length; drop malformed packets
- Rebuild containers from alpine/debian/ubi base images; refresh
libssl/openssl-libs - Detect: WAF/IDS rules for short QUIC CIDs, abnormal CMS OID bytes, CMP failure modes
- Version hygiene: pin OpenSSL in SBOM; CI alert on OpenSSL CVSS threshold so patch versions are not skipped
Sources
- OpenSSL Security Advisory index
- CVE-Bund federal advisory: WID-SEC-2026-0995
- SecurityOnline: OpenSSL Security Update August 2026
- CN-SEC: OpenSSL 9-vulnerability analysis