CVE-2026-28386
OpenSSL vulnerability analysis and mitigation

Overview

CVE-2026-28386 is an out-of-bounds read vulnerability in OpenSSL's AES-CFB128 implementation on x86-64 systems with AVX-512 and VAES instruction support. It affects OpenSSL versions 3.6.0 through 3.6.1 (fixed in 3.6.2), specifically the OpenSSL FIPS module. The vulnerability was disclosed on April 7, 2026, with a patch committed on April 6, 2026. OpenSSL assessed it as Low severity internally, though the CVSS v3.1 base score is 7.5 (High) per NVD (OpenSSL Advisory, GitHub Advisory).

Technical details

The root cause (CWE-125: Out-of-bounds Read) lies in the partial-block pre-processing code within ossl_aes_cfb128_vaes_enc and ossl_aes_cfb128_vaes_dec in crypto/aes/asm/aes-cfb-avx512.pl. These functions used unmasked vmovdqu8 instructions to unconditionally load 16 bytes from the input buffer even when fewer bytes were valid, potentially reading 1–15 bytes beyond the buffer end. The fix replaces the unmasked loads with masked loads (vmovdqu8 (%r11),%xmm0{%k1}{z} and vmovdqu8 ($inp),%xmm1{%k1}{z}), consistent with the correct approach already used in the post-processing code. Exploitation requires three simultaneous conditions: the system must be x86-64 with AVX-512/VAES support, the application must use AES-CFB128 mode with partial block processing across multiple calls, and the input buffer must end at a memory page boundary with the next page unmapped (OpenSSL Commit, OpenSSL Advisory).

Impact

The primary impact is a Denial of Service (DoS): if the over-read crosses an unmapped memory page boundary, the application crashes. There is no confidentiality impact, as the over-read bytes are not written to output or otherwise disclosed. The vulnerability does not affect TLS/DTLS protocols (which use CBC, GCM, CCM, or ChaCha20-Poly1305), significantly limiting real-world exposure to applications explicitly using AES-CFB128 mode on affected hardware (OpenSSL Advisory, GitHub Advisory).

Mitigation and workarounds

Upgrade OpenSSL to version 3.6.2 or later, which contains the fix for this vulnerability (OpenSSL Advisory, OpenSSL Commit). Organizations that cannot immediately upgrade should prioritize systems meeting all three conditions: x86-64 architecture with AVX-512/VAES support, use of AES-CFB128 encryption mode, and multi-call partial block processing patterns. Systems using only TLS/DTLS with standard cipher modes (CBC, GCM, CCM, ChaCha20-Poly1305) are not affected and can deprioritize patching accordingly.

Community reactions

The release of OpenSSL 3.6.2 received coverage from Linux-focused outlets including 9to5Linux, Linuxiac, and Help Net Security, which highlighted the security fixes bundled in the release (Help Net Security). Security news sites such as CyberSecurityNews and IT Security News also covered the broader set of CVEs fixed in OpenSSL 3.6.2. Community reaction was generally measured, reflecting the narrow exploitation conditions and OpenSSL's own Low severity assessment, with no significant alarm or controversy noted.

Additional resources


SourceThis report was generated using AI

Related OpenSSL vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-45447HIGH8.8
  • OpenSSL logoOpenSSL
  • libopenssl1_1-32bit
NoYesJun 09, 2026
CVE-2026-11999HIGH8.2
  • OpenSSL logoOpenSSL
  • openssl1.0
NoYesJun 25, 2026
CVE-2026-7383HIGH8.1
  • OpenSSL logoOpenSSL
  • openssl-debuginfo
NoYesJun 09, 2026
CVE-2026-9076HIGH7.5
  • OpenSSL logoOpenSSL
  • libopenssl-1_0_0-devel
NoYesJun 09, 2026
CVE-2026-45784MEDIUM5.1
  • Rust logoRust
  • deno
NoYesJul 17, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management