Loading story…
Two high-severity vulnerabilities were disclosed in rust-openssl, the Rust bindings for OpenSSL, affecting multiple 0.9.x and 0.10.x releases prior to 0.10.78. CVE-2026-41898 affects versions from 0.9.24 up to, but not including, 0.10.78, where several FFI trampoline callback paths passed a closure-returned usize to OpenSSL without validating it against the output buffer size. The flaw can trigger buffer overflows and leak adjacent memory to a network peer, and it is mapped to CWE-126 and CWE-130.
A second issue, CVE-2026-41681, affects versions from 0.10.39 up to, but not including, 0.10.78, in MdCtxRef::digest_final(), which writes EVP_MD_CTX_size(ctx) bytes to the caller buffer without checking whether the buffer is large enough. The resulting out-of-bounds write can cause stack corruption and is reachable from safe Rust, with the weakness classified as CWE-121. Both vulnerabilities were addressed in rust-openssl 0.10.78, with public advisories, code references, and fix details released alongside the CVE records.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
4 events from the most recent confirmed update back to the earliest known activity.
CVE-2026-41898 was published for rust-openssl, affecting versions 0.9.24 through before 0.10.78. The issue stems from FFI trampoline callback paths forwarding a closure-returned length to OpenSSL without validating it against the output buffer, potentially leaking adjacent memory or causing overflow-related behavior.
CVE-2026-41681 was published for rust-openssl, affecting versions 0.10.39 through before 0.10.78. The flaw allows MdCtxRef::digest_final() to write past a caller-provided buffer because no length check is performed before EVP_DigestFinal() writes the digest output.
rust-openssl version 0.10.78 was released with fixes for two vulnerabilities: unchecked callback-returned lengths in PSK and cookie trampolines, and a missing output-length check in MdCtxRef::digest_final(). The fixes addressed affected version ranges below 0.10.78 referenced by later advisories.
The rust-openssl project released openssl-v0.10.78 on 2026-04-19 to address five security vulnerabilities disclosed via GitHub Security Advisories. The fixes covered multiple memory-safety issues, including key derivation, PEM password callback handling, AES key unwrap bounds checking, digest finalization, and unchecked callback-returned lengths in PSK and cookie trampolines.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
3 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcecvefeed.io
Open sourceseclists.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 released a security update on January 27, 2026**, addressing **12 vulnerabilities** across supported branches, including **one High-severity issue with potential remote code execution (RCE)**, one Moderate, and multiple Low-severity flaws. The most serious vulnerability, **CVE-2025-15467 (High)**, is a **pre-authentication stack buffer overflow** in **CMS `AuthEnvelopedData` parsing** when using AEAD ciphers (e.g., **AES-GCM**); a crafted CMS message with an **oversized IV in ASN.1 parameters** can trigger a crash and may enable code execution in applications that parse **untrusted CMS/PKCS#7 content** (notably **S/MIME** workflows). Both sources emphasize that while **DoS is the most likely outcome in many environments**, the presence of a stack write primitive makes the issue operationally significant where untrusted CMS is processed. A second notable issue, **CVE-2025-11187 (Moderate)**, involves a **stack overflow during PKCS#12 MAC verification** (PBMAC1/PBKDF2-related validation), where attacker-controlled parameters (e.g., key length) can lead to crashes and potentially more severe impact when processing **untrusted PKCS#12 files** (e.g., certificate import/export, PKI/CA tooling). Affected versions called out include **OpenSSL 3.x** (with additional low-severity issues spanning older branches such as **1.0.2 and 1.1.1**), and patched releases include **3.6.1, 3.5.5, 3.4.4, 3.3.6, and 3.0.19** (with corresponding fixes for older maintained lines). Datadog notes **OpenSSL 3.x FIPS modules are not affected** by the highlighted CMS and PKCS#12 overflow issues, and both sources point to higher risk in services that ingest these formats from external or user-supplied inputs (e.g., S/MIME gateways, certificate management services).
Jun 29, 2026