CVE-2026-41678: Openssl · Out-of-bounds write in `aes::unwrap_key`
Affects opensslSource GCVE Database
Not known to be exploited : upgrade to 0.10.78 soon.
Data as of 9 Nov 2026, 17:35 UTC
Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
- Patch
- Available – fixed in 0.10.78
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Apr 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 9 Nov 2026.
What to do
Upgrade openssl to 0.10.78.
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 Rust bindings to version 0.10.78 or later, where the assertion checking output buffer size is corrected and prevents out-of-bounds writes by panicking on insufficient buffer size. No other mitigations are indicated.
Description
A vulnerability in OpenSSL's Rust binding function `openssl::aes::unwrap_key` allows an out-of-bounds write due to incorrect buffer size validation. The function incorrectly accepts output buffers that are too small, leading to memory corruption. This flaw was introduced in version 0.10.24 and fixed in 0.10.78 by correcting the assertion to panic when the output buffer is too small.