Loading story…
OpenSSL released fixes for CVE-2026-84782, a high-severity DTLS handshake retransmission flaw that can allow a connected peer to disclose adjacent heap memory in plaintext or crash an affected application. The out-of-bounds read occurs when retransmission starts while transmission of a fragmented handshake message is suspended, leaving OpenSSL with an incorrect buffer position. CISA assigned the issue a CVSS score of 8.2; no exploitation was known as of September 29, 2026, and OpenSSL has published no workaround.
Organizations should update to OpenSSL 4.0.3, 3.6.5, 3.5.9, or 3.4.8, or install their vendor’s corrected package. The flaw also affects 3.0, 1.1.1, and 1.0.2, but patches for those older branches require premium support. OpenSSL 3.0 reached public end of life on September 7, 2026 and no longer receives publicly available security fixes, increasing upgrade urgency; OpenSSL recommends moving to the 3.5 LTS release, supported through April 2030, or OpenSSL 4.0. The vulnerable DTLS logic lies outside the FIPS module boundary.
See affected versions and whether adversaries are exploiting it.
19 events from the most recent confirmed update back to the earliest known activity.
SUSE released advisory SUSE-SU-2026:4419-1 with OpenSSL 3 package updates for SLES 15 and SLES for SAP 15, addressing CVE-2026-35189, CVE-2026-54872, CVE-2026-75805, CVE-2026-75806, CVE-2026-77696, and CVE-2026-84782. The fixes cover memory-allocation, timing side-channel, NULL-pointer dereference, and DTLS denial-of-service and retransmission flaws.
SUSE published security update SUSE-SU-2026:4418-1 addressing CVE-2026-84782 in the openssl-3-livepatches package on SUSE Linux Enterprise Server 15. The prescribed remediation is to update the affected package.
TuxCare published a CentOS 8 security update under advisory CLSA-2026-1790933563 covering CVE-2026-35189 and CVE-2026-84782, rated Important. The Tenable record identifies the patch publication date but does not specify affected packages or fixed package versions.
TuxCare published a CentOS 8.5 security update under advisory CLSA-2026-1790933161 covering CVE-2026-35189 and CVE-2026-84782, rated Important. The Tenable record dates patch publication to October 2, 2026, but does not specify affected packages or fixed package versions.
TuxCare published a CentOS 8.4 security update under advisory CLSA-2026-1790933443 covering CVE-2026-35189 and CVE-2026-84782, rated Important. The Tenable listing records the patch publication but does not specify affected packages or fixed package versions.
The Canadian Centre for Cyber Security published advisory AV26-980 covering multiple OpenSSL vulnerabilities and identifying releases earlier than 1.0.2zs, 1.1.1zj, 3.0.23, 3.4.8, 3.5.9, 3.6.5, and 4.0.3 as affected. It recommended that users review OpenSSL vulnerability information and apply necessary updates as available.
The CVE record explained that a DTLS handshake write suspended with WANT_WRITE could share buffer-position and write-state data with a timer-triggered retransmission, causing an incorrect retransmission offset, heap-memory disclosure, or inconsistent state and process termination. OpenSSL corrected this by resetting the retransmission read position and deferring retransmissions while a handshake write remains suspended.
OpenSSL's September 29 advisory detailed low-severity flaws affecting QUIC, CMP, DTLS, TLS, and EC/SM2 cryptography, including several denial-of-service and timing/cache side-channel issues. It also identified CVE-2026-54873 as a QUIC stream-frame memory-retention flaw and stated that none of the 14 listed vulnerabilities affects the FIPS module boundary.
A vulnerability identified as CVE-2026-54873 was published affecting OpenSSL-related and associated platform packages on CentOS 7 and 8 and RHEL 7 through 10. The notice reported no known exploits and did not provide technical details or remediation guidance.
The September 29 OpenSSL releases also fixed CVE-2026-84783, a moderate-severity flaw that can crash certain multi-threaded TLS clients or servers requesting client certificates, and CVE-2026-75806, a low-severity DTLS 1.2 connection-termination issue.
Ubuntu fixed CVE-2026-84782 in libssl3t64 packages for Ubuntu 26.04 LTS and 24.04 LTS, and in libssl3 for Ubuntu 22.04 LTS. Ubuntu advised users to reboot after installing the updates.
CISA assigned CVE-2026-84782 a CVSS score of 8.2 and recorded no known exploitation at that time.
OpenSSL disclosed CVE-2026-84782, a high-severity DTLS out-of-bounds read that can expose adjacent heap memory to a connected peer or crash the process. It released public fixes in 4.0.3, 3.6.5, 3.5.9, and 3.4.8; fixes for 3.0, 1.1.1, and 1.0.2 were restricted to premium-support customers.
OpenSSL 3.0 reached end of life after its five-year LTS support period and stopped receiving publicly available security fixes. Extended paid support remained available.
Laurent Gaffie of Secorizon reported the DTLS retransmission vulnerability later assigned CVE-2026-84782 to OpenSSL. Ryan Hooper subsequently developed the correction.
OpenSSL released the 3.0 series as a long-term-support version, beginning its five-year public-support period.
The Guyana National CIRT advised users and administrators to review OpenSSL’s September 29 security advisory and apply necessary updates. Its notice identified releases earlier than 1.0.2zs, 1.1.1zj, 3.0.23, 3.4.8, 3.5.9, 3.6.5, and 4.0.3 as affected.
Debian fixed CVE-2026-84782 in Debian 13 through openssl version 3.5.7-1~deb13u3, released as DSA-6531-1. Debian 12 remained listed as vulnerable as of September 30.
OpenSSL security updates addressed 14 vulnerabilities, including four rated high severity, which could enable denial of service or disclosure of sensitive information. The updates cover affected 4.x, 3.6.x, 3.5.x, 3.4.x, 3.0.x, 1.1.x, and 1.0.x releases, with fixed-version thresholds specified for each branch.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
29 references tracked. Mallory keeps watching after this page renders.
linuxsecurity.com
Open sourcetenable.com
Open sourcetenable.com
Open sourcetenable.com
Open sourceopenssl-library.org
Open sourcecve.org
Open sourceopenssl-library.org
Open sourcegithub.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 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.
Aug 31, 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 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