Quick answers
- Is CVE-2026-41678 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41678 being exploited in the wild.
- How severe is CVE-2026-41678?
- High severity, with a CVSS score of 8.1, published 24 April 2026.
- Which products and versions are affected?
- openssl (crates.io) SEMVER:introduced=0.10.24,fixed=0.10.78.
- Is there a fix for CVE-2026-41678?
- Yes. openssl (crates.io): upgrade to 0.10.78 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-41678 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-41678?
- Check whether you run openssl (crates.io) or Rust-Openssl Project Rust-Openssl at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- openssl (crates.io): upgrade to 0.10.78 or later
cargo update -p openssl
Technical details
An out-of-bounds write vulnerability exists in the aes::unwrap_key() function of rust-openssl due to an inverted bounds check assertion. The function incorrectly validates the output buffer size using 'out.len() + 8 <= in_.len()' instead of ensuring the buffer is large enough ('out.len() >= in_.len() - 8'). Consequently, the function rejects sufficiently large buffers and accepts those that are too small, leading to a memory write past the end of the buffer. This can be triggered via network-reachable vectors if an application allows attacker-controlled buffer sizes. The issue is fixed in version 0.10.78.
Affected products
- rust-openssl project rust-openssl >= 0.10.24, < 0.10.78
Identifiers
- CVE-2026-41678
- GHSA-8c75-8mhr-p7r9
- RUSTSEC-2026-0463
Timeline
- 2026-04-19: advisory: GitHub security advisory published
- 2026-04-24: disclosed: CVE published to NVD