Loading story…
The OpenSSL Project released OpenSSL 4.1 Alpha 1 as a testing-only pre-release, introducing initial support for DTLS 1.3, TLS GREASE under RFC 8701, DTLS in the SSL listener API, and the IKEv2 key-derivation function. DTLS 1.3 brings faster handshakes, forward secrecy, post-quantum cryptography support, and a more efficient record-header format, while GREASE injects reserved values into TLS handshakes to expose interoperability defects.
The release adds AVX-512 optimizations for SHAKE x4 operations used by ML-DSA and AES-CBC decryption, alongside initial support for the Elbrus 2000/E2K architecture. It also removes support for Windows on Itanium and Windows CE and includes build and configuration compatibility changes. OpenSSL warned that the alpha software is not suitable for security-critical deployment.
Track how attackers are adapting to this technology.
1 event from the most recent confirmed update back to the earliest known activity.
The OpenSSL Project released the OpenSSL 4.1 Alpha1 feature pre-release for testing only, warning that it must not be used for security-critical purposes. The release adds DTLS 1.3, RFC 8701 GREASE, DTLS listener API and IKEv2 KDF support, plus initial Elbrus2000 support and platform-specific cryptographic optimizations.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Follow how adversaries are adapting to this technology, and where it touches your stack today.
9 references tracked. Mallory keeps watching after this page renders.
cryptika.com
Open sourcecybersecuritynews.com
Open sourcehelpnetsecurity.com
Open sourcephoronix.com
Open sourceopenssl-library.org
Open sourceopenssl-library.org
Open sourcegithub.com
Open sourcegithub.com
Open sourcedatatracker.ietf.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.
The OpenSSL Project released updated versions across multiple supported branches to fix a set of security flaws in the SSL/TLS toolkit, with **OpenSSL 3.6.2** carrying the broadest set of patches. The updates address issues including incorrect failure handling in RSA KEM `RSASVE` encapsulation, an out-of-bounds read in `AES-CFB-128` on x86-64 systems with `AVX-512` support, a potential use-after-free in DANE client code, several `NULL` pointer dereference bugs, and a heap buffer overflow in hexadecimal conversion. OpenSSL said the most severe issue in the release was rated **Moderate**. Additional releases — **3.5.6, 3.4.5, 3.3.7, 3.0.20, 1.1.1zg, and 1.0.2zp** — also shipped with security fixes and minor bug corrections, though older branches received smaller subsets of the patches. The 3.6.2 release also repaired two regressions introduced in 3.6.0 affecting `X509_V_FLAG_CRL_CHECK_ALL` behavior and stapled OCSP response handling that could trigger handshake failures. Administrators running **OpenSSL 3.6.x** on x86-64 systems with `AVX-512` enabled were specifically urged to prioritize the `AES-CFB-128` fix because of memory-read exposure.
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
OpenSSL remediated three vulnerabilities: **CVE-2019-1547**, an ECDSA timing side channel that could expose private keys when applications use explicit EC parameters without a cofactor; **CVE-2019-1549**, in which OpenSSL 1.1.1–1.1.1c may allow parent and child processes to share RNG state after `fork()`; and **CVE-2019-1563**, a Bleichenbacher-style RSA padding oracle in CMS/PKCS#7 decryption. Exploiting the ECDSA and CMS issues requires many observed signature timings or chosen-ciphertext decryption attempts, respectively; normal TLS use through `libssl` is not affected by CVE-2019-1547. Upstream fixes are available in OpenSSL 1.1.1d, 1.1.0l, and 1.0.2t, with CVE-2019-1549 fixed in 1.1.1d. Red Hat shipped backported fixes for affected JBoss Core Services Apache HTTP Server packages and RHEL 8 OpenSSL packages, advising customers to restart OpenSSL-linked services or reboot after installation. Slackware also released updated OpenSSL packages for 14.2 and -current. Organizations should patch supported OpenSSL deployments and prioritize review of applications that use explicit EC parameters, CMS/PKCS#7 RSA decryption, or forked processes relying on cryptographic randomness.
Aug 28, 2026