Loading story…
OpenSSL released fixes for eight Moderate- and Low-severity vulnerabilities across supported branches, affecting QUIC, CMS, CMP, DTLS, TLS Raw Public Key processing, and AEAD decryption. The most significant issues are a QUIC INITIAL-packet double free (CVE-2026-18798), a CMS key-unwrapping heap buffer overflow (CVE-2026-63072), and a CMP invalid-pointer dereference triggered through a crafted protectionAlg value (CVE-2026-63076). Most flaws can cause denial of service through crashes, heap corruption, or memory exhaustion.
Organizations should upgrade to OpenSSL 4.0.2, 3.6.4, 3.5.8, 3.4.7, or 3.0.22; premium-support customers using legacy branches should update to 1.1.1zi or 1.0.2zr where applicable. Affected releases include versions before those fixes across the 1.0.2, 1.1.1, 3.0, 3.4, 3.5, 3.6, and 4.0 branches. OpenSSL stated that none of the disclosed vulnerabilities affects its FIPS module, as the vulnerable paths are outside the FIPS boundary or involve non-FIPS-approved algorithms.
See real exploitation activity before you spend the cycle.
7 events from the most recent confirmed update back to the earliest known activity.
Debian issued DSA-6465-1 for Debian 13 (trixie), addressing ten OpenSSL vulnerabilities, including CVE-2026-54874 and CVE-2026-63072 through CVE-2026-63076. The issues were fixed in OpenSSL version 3.5.7-1~deb13u2, and administrators were advised to upgrade affected OpenSSL packages.
The Canadian Centre for Cyber Security published advisory AV26-846 concerning OpenSSL vulnerabilities affecting releases prior to 1.0.2zr, 1.1.1zi, 3.0.22, 3.4.7, 3.5.8, 3.6.4, and 4.0.2. It encouraged users and administrators to review OpenSSL vulnerability information and apply necessary updates.
The OpenSSL Software Foundation published the CVE-2026-54874 record, documenting that forged future-epoch DTLS records can cause vulnerable endpoints to retain approximately 16 KB buffers for up to 100 records per association. The record estimates roughly 1.7 MB retained memory per connection and a network-to-memory amplification factor of about 1200, enabling remote memory-exhaustion denial of service.
The OpenSSL Software Foundation published CVE-2026-63072, documenting a CWE-787 heap buffer overflow in CMS_decrypt() when AES-WRAP-PAD is selected. A crafted CMS message can cause a deterministic eight-byte zero write beyond a heap buffer, typically causing denial of service; OpenSSL fixed it by allocating the unwrap buffer for worst-case output size.
OpenSSL issued a security advisory disclosing eight Moderate- and Low-severity vulnerabilities affecting QUIC, CMS, CMP, DTLS, TLS Raw Public Key handling, and AEAD behavior. The advisory recommended upgrading to OpenSSL 4.0.2, 3.6.4, 3.5.8, 3.4.7, or 3.0.22, and to 1.1.1zi or 1.0.2zr for applicable premium-support customers.
OpenSSL committed a0c8ec5 to the openssl-3.0 branch to fix CVE-2026-63072 in CMS AES-WRAP-PAD unwrapping. The patch allocates the larger of the predicted output length and input length, preventing an integrity-failure path from causing an eight-byte out-of-bounds heap write.
Amazon Web Services reported CVE-2026-54874, a DTLS handshake resource-consumption vulnerability that can enable remote memory-exhaustion denial of service, to OpenSSL. Matt Caswell developed the fix.
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.
15 references tracked. Mallory keeps watching after this page renders.
gmcsirt.gm
Open sourcecybersecuritynews.com
Open sourcecirt.gy
Open sourcemalware.news
Open sourcetenable.com
Open sourcecve.org
Open sourcegithub.com
Open sourceopenssl-library.org
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 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 fixes for seven vulnerabilities across multiple supported branches, led by **CVE-2026-31790**, a Moderate-severity flaw in RSA KEM `RSASVE` encapsulation that can leak stale or uninitialized memory to a malicious peer. The issue can be triggered when applications process attacker-supplied invalid RSA public keys without validating them first. The advisory also disclosed six Low-severity bugs: an AVX-512/VAES-specific out-of-bounds read in AES-CFB-128, a potential use-after-free or double-free in DANE client code, two CMS-related NULL pointer dereferences, a delta CRL NULL dereference, and a heap buffer overflow in hexadecimal conversion on 32-bit platforms. The project advised users to upgrade to fixed releases **3.0.20**, **3.3.7**, **3.4.5**, **3.5.6**, and **3.6.2**, with premium-support fixes available for **1.1.1zg** and **1.0.2zp** where applicable. OpenSSL said branches **3.1** and **3.2** are out of support and were not analyzed, leaving organizations running those versions without reviewed fixes in this advisory.
Jun 29, 2026
OpenSSL maintainers released urgent security updates to address three newly discovered vulnerabilities affecting all supported versions of the widely used SSL/TLS library. The vulnerabilities, tracked as CVE-2025-9230, CVE-2025-9231, and CVE-2025-9232, pose risks including key recovery, remote code execution, and denial-of-service attacks. One of the flaws, CVE-2025-9230, involves an out-of-bounds read and write in the CMS decryption process with password-based encryption (PWRI), which could lead to application crashes or memory corruption, potentially allowing attackers to execute arbitrary code. Although the use of PWRI is rare, the consequences of successful exploitation could be severe, prompting OpenSSL to rate the flaw as moderate in severity. FIPS modules are not affected by this vulnerability. Another vulnerability, CVE-2025-9231, is a timing side-channel issue in SM2 signature computations on 64-bit ARM platforms, which could enable attackers to recover private keys through precise timing measurements. While OpenSSL does not natively support SM2 keys in TLS, the risk remains for applications using SM2 signatures. The third flaw, CVE-2025-9232, details were not fully elaborated in the available sources, but it is included in the urgent patch set. OpenSSL has released patched versions 3.5.4, 3.4.3, 3.3.5, 3.2.6, 3.0.18, 1.0.2zm, and 1.1.1zd to address these vulnerabilities. Security experts and the OpenSSL Project strongly urge all users and organizations to update to the latest versions immediately to mitigate the risk of exploitation. The vulnerabilities impact a broad range of systems and applications that rely on OpenSSL for secure communications, making prompt patching critical for maintaining the confidentiality and integrity of data in transit. The flaws could be exploited in scenarios where attackers have access to cryptographic operations or can induce specific decryption processes. The OpenSSL advisory emphasizes that, despite the low probability of successful exploitation for some of the flaws, the potential impact warrants immediate attention. Organizations are advised to review their use of OpenSSL, especially in environments utilizing ARM platforms or custom cryptographic implementations. The updates are part of OpenSSL's ongoing commitment to maintaining the security of its cryptographic library, which underpins much of the internet's secure traffic. Security researchers continue to scrutinize OpenSSL due to its widespread deployment and critical role in protecting sensitive information. The release of these patches highlights the importance of timely vulnerability management and the need for organizations to monitor security advisories from key software suppliers. Failure to apply these updates could leave systems exposed to advanced attacks, including those that bypass traditional security controls. The OpenSSL Project's rapid response demonstrates the collaborative effort between researchers and maintainers to address security issues before they can be widely exploited.
Jun 29, 2026