CVE-2026-44662: Openssl · Buffer overflow with AES key wrap with padding in `cipher_update`
Affects opensslSource GCVE Database
Not known to be exploited : upgrade to 0.10.79 soon.
Data as of 10 Nov 2026, 14:22 UTC
Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
- Patch
- Available – fixed in 0.10.79
Exploitation evidence
Disclosed: evidence found.
CVE published 4 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade openssl to 0.10.79.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
crates.ioopensslpkg:cargo/opensslOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade OpenSSL to version 0.10.79 or later, where this buffer overflow issue is fixed. Users relying on AES key-wrap-with-padding ciphers should prioritize this update to prevent heap corruption risks.
Description
A buffer overflow vulnerability exists in OpenSSL's AES key-wrap-with-padding cipher implementations prior to version 0.10.79. The issue occurs because the output buffer allocation does not account correctly for padding, causing writes up to 7 bytes beyond the buffer when input lengths are not multiples of 8. This leads to heap corruption that an attacker can partially control if they influence the plaintext length.