CVE-2026-28386 is an out-of-bounds read vulnerability in OpenSSL’s AES-CFB128 encryption and decryption implementation on x86-64 systems that use the AVX-512 and VAES optimized code path. When processing partial cipher blocks, the affected implementation can read up to 15 bytes past the end of the input buffer. The vulnerable path is reached only in a specific state: a previous call must have left an incomplete block, and a subsequent call must provide fewer bytes than are needed to complete that block. The issue affects OpenSSL 3.6 and the OpenSSL 3.6 FIPS module; other architectures and systems without VAES support use different code paths and are not affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An out-of-bounds read in AES-CFB-128 affecting x86-64 CPUs with AVX-512 support in OpenSSL.
An out-of-bounds read in the AES-CFB-128 AVX-512 implementation on x86-64 systems, leading to memory-read exposure and potential information disclosure.
Out-of-bounds read in AES-CFB-128 on x86-64 systems with AVX-512 support in OpenSSL.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.