Do Son 
TL;DR
OpenSSL shipped a security update on August 25, 2026, fixing nine vulnerabilities. Two rank as Moderate, and the rest are Low. Most lead to denial of service, so admins should patch soon.
Why This OpenSSL Security Update Matters
OpenSSL runs beneath much of the internet’s encrypted traffic. As a result, a single flaw can ripple across servers, apps, and devices. This OpenSSL security update touches QUIC, DTLS, CMS, and the CMP protocol.
None of the nine bugs allow remote code execution, according to the project. Instead, most enable denial of service. Still, uptime matters, and attackers can crash exposed services with little effort.
How the Attacks Work
Two Moderate Flaws
The first Moderate bug is a QUIC double free, tracked as CVE-2026-18798. A malformed INITIAL packet can crash a QUIC server. The advisory notes the packet needs a destination connection ID shorter than 8 bytes.
The second, CVE-2026-63072, is a heap buffer overflow in CMS key unwrapping. An attacker changes a single OID byte in a crafted message. Consequently, decryption writes 8 bytes past the allocation.
Low-Severity Issues
The remaining flaws affect CMP, DTLS, RPK, and AEAD handling. Several let a malicious or on-path server crash a client. For example, CVE-2026-63073 passes an attacker-controlled sender name straight into a format string.
OpenSSL sums up the CMP pointer bug plainly. The advisory says a remote attacker can crash a CMP server, resulting in a Denial of Service.
Another AEAD flaw may let forged empty-ciphertext messages pass tag checks.
Is It Being Exploited?
No exploitation in the wild has been confirmed. Likewise, the project reports no public proof-of-concept. The QUIC double free is judged highly improbable to allow code execution.
Affected Versions
The affected branches vary by CVE. Broadly, OpenSSL 4.0, 3.6, 3.5, 3.4, and 3.0 face one or more issues. Older 1.1.1 and 1.0.2 branches are affected only in select cases.
The project analyzed only supported releases. Therefore versions 3.1, 3.2, and 3.3 were not reviewed, since they are end of life.
Patch and Mitigation Steps
Update to the fixed release for your branch. You can review the full OpenSSL security update advisory for exact version numbers.
- OpenSSL 4.0 users should move to 4.0.2.
- OpenSSL 3.6 users should move to 3.6.4.
- OpenSSL 3.5 users should move to 3.5.8.
- OpenSSL 3.4 users should move to 3.4.7.
- OpenSSL 3.0 users should move to 3.0.22.
Premium support customers on 1.1.1 and 1.0.2 have separate patched builds. If you cannot patch at once, limit exposure of QUIC, DTLS, and CMP endpoints. Prompt updates remain the safest fix.
Support Our Threat Intelligence
Find our zero-day alerts and CVE reports helpful? Support our work today and unlock a 100% ad-free reading experience!
Buy Me a Coffee
PayPal
