Loading story…
OpenSSL released 1.1.0c to remediate three vulnerabilities in the 1.1.0 branch, led by CVE-2016-7054, a high-severity heap-buffer overflow in ChaCha20/Poly1305 processing. A remote attacker could send a large malformed payload to TLS services using *-CHACHA20-POLY1305 cipher suites and crash the affected OpenSSL process, creating a denial-of-service condition. The release also fixes CVE-2016-7053, a CMS NULL-pointer dereference, and CVE-2016-7055, a Montgomery multiplication issue; the latter also affects 1.0.2.x and was slated for a subsequent 1.0.2 update.
Administrators running OpenSSL 1.1.0 should upgrade to 1.1.0c. The flaws do not affect SSL/TLS certificates, so certificate replacement or revocation is not required. Organizations should also remove obsolete OpenSSL branches from production: versions 0.9.8 and 1.0.0 were already unsupported, and support for 1.0.1 was scheduled to end on 31 December 2016.
See real exploitation activity before you spend the cycle.
9 events from the most recent confirmed update back to the earliest known activity.
Tyler Nighswander of ForAllSecure reported CVE-2016-7053 to OpenSSL. The moderate-severity flaw could cause applications parsing invalid CMS structures to crash through a NULL-pointer dereference.
OpenSSL's security advisory rated CVE-2016-6309 as critical and identified it as a use-after-free flaw in OpenSSL 1.1.0a, introduced by the prior CVE-2016-6307 fix. The related 1.1.0b and 1.0.2j patches addressed CVE-2016-6309 and the moderate CRL null-pointer crash CVE-2016-7052.
Robert Święcki of Google's Security Team reported CVE-2016-7054 to OpenSSL using honggfuzz. The high-severity heap-buffer overflow could crash TLS services using ChaCha20/Poly1305 cipher suites when supplied a large corrupted payload.
OpenSSL published a security advisory listing vulnerabilities addressed by releases 1.0.2f and 1.0.1r, including a high-severity flaw affecting the 1.0.2 branch and an SSLv2-handshake issue affecting 1.0.2 and 1.0.1. The release also raised the minimum accepted handshake size to 1024 bits as Logjam-related hardening.
OpenSSL versions 0.9.8 and 1.0.0 ceased receiving support and security updates. OpenSSL stated that no further patches would be issued for those branches.
OpenSSL published an advisory covering CVE-2016-7054, CVE-2016-7053, and CVE-2016-7055, and released OpenSSL 1.1.0c to remediate the three flaws in the 1.1.0 branch. The advisory noted that the 1.0.2 fix for the low-severity Montgomery multiplication issue CVE-2016-7055 was deferred to a subsequent 1.0.2 release.
OpenSSL released versions 1.1.0a, 1.0.2i, and 1.0.1u to fix 14 vulnerabilities. The most serious, CVE-2016-6304, allowed repeated renegotiation with large OCSP Status Request extensions to exhaust server memory and cause denial of service.
OpenSSL released versions 1.0.2g and 1.0.1s to remediate seven vulnerabilities, including the high-severity DROWN cross-protocol attack. DROWN could permit decryption of TLS sessions where a server supported SSLv2 and EXPORT ciphers as a Bleichenbacher RSA padding oracle.
OpenSSL released versions 1.0.2b, 1.0.1n, 1.0.0s, and 0.9.8zg to address six newly discovered vulnerabilities, five rated moderate risk and one low risk. The project advised administrators to upgrade affected installations.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
7 references tracked. Mallory keeps watching after this page renders.
digicert.com
Open sourcedigicert.com
Open sourcedigicert.com
Open sourceopenssl.org
Open sourcedigicert.com
Open sourcedigicert.com
Open sourcedigicert.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
OpenSSL released fixes for seven vulnerabilities affecting older 1.0.1 and 1.0.2 branches, including high-severity `CVE-2016-2108`, an ASN.1 parsing and encoding flaw that can cause an out-of-bounds write and potentially exploitable memory corruption when untrusted ASN.1 data with `ANY` fields is reserialized. The release also fixed `CVE-2016-2107`, which permits a man-in-the-middle TLS/DTLS AES-CBC padding-oracle attack on AES-NI-capable servers, alongside denial-of-service, excessive-allocation, and EBCDIC overread issues. The update additionally remediates heap-corruption defects `CVE-2016-2105` and `CVE-2016-2106` in the `EVP_EncodeUpdate()` and `EVP_EncryptUpdate()` APIs, respectively. Applications that directly submit exceptionally large input to these APIs may be vulnerable, while OpenSSL’s bounded internal PEM uses were not affected. OpenSSL issued versions 1.0.2h and 1.0.1t for most fixes, and Red Hat shipped patched RHEL 6 and RHEL 6.7 EUS packages; affected organizations should update and restart OpenSSL-linked services or reboot systems.
Aug 29, 2026
OpenSSL disclosed a broad set of vulnerabilities affecting ASN.1 parsing, PKCS#12, CMS/PKCS#7, QUIC, OCSP, CMP/CRMF, DH key validation, AEAD cipher handling, and certificate and email validation across the 4.0, 3.6, 3.5, 3.4, and 3.0 branches. The most severe issue, **CVE-2026-45447**, is a high-severity heap use-after-free in `PKCS7_verify()` that can be triggered by specially crafted PKCS#7 or S/MIME signed messages and could lead to crashes, heap corruption, or potentially remote code execution. The advisory also details moderate-severity flaws that could enable forged CMS `AuthEnvelopedData` messages, denial-of-service conditions in QUIC and OCSP processing, a TLS client double-free via OCSP stapling, a QUIC server `NULL` dereference, and cryptographic failures in AES-OCB when applications use the `EVP_Cipher()` one-shot API, alongside numerous lower-severity parsing, validation, and bounds-checking bugs. OpenSSL said most issues were fixed in **4.0.1**, **3.6.3**, **3.5.7**, **3.4.6**, and **3.0.21**, with **1.1.1zh** and **1.0.2zq** issued for supported legacy customers; most flaws were reported as outside the OpenSSL FIPS module boundary, except **CVE-2026-42770**, which affects FIPS modules in multiple supported branches.
Jun 29, 2026
OpenSSL released updates **1.1.0d** and **1.0.2k** to address several Moderate-severity defects, including `CVE-2017-3731`, an integer-underflow out-of-bounds read that lets specially truncated TLS packets crash affected 32-bit clients or servers using vulnerable cipher suites such as RC4-MD5. The releases also addressed `CVE-2017-3730`, in which malicious DHE or ECDHE parameters can trigger a NULL-pointer dereference in clients, and `CVE-2017-3732`, a carry-propagation flaw in x86_64 Montgomery squaring that can yield incorrect cryptographic results. Exploiting the latter against RSA or DSA is considered highly impractical; a Diffie-Hellman attack is more feasible only under restrictive conditions involving unpatched systems, persistent shared DH parameters, and substantial resources. Red Hat shipped updated OpenSSL packages for RHEL 6 and 7 through **RHSA-2017:0286**, remediating `CVE-2017-3731` and `CVE-2016-8610`. The latter allows unauthenticated attackers to send large volumes of malformed plaintext TLS/SSL ALERT messages during handshakes, consuming server CPU and preventing new connections; Nginx deployments were identified as affected, while Apache HTTP Server was not. Organizations should apply the vendor updates, restart all services linked to OpenSSL or reboot hosts, disable RC4-MD5 where updates cannot be immediately deployed, and retire unsupported OpenSSL 1.0.1, 1.0.0, and 0.9.8 installations.
Aug 29, 2026