Quick answers
- Is CVE-2026-44662 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44662 being exploited in the wild.
- How severe is CVE-2026-44662?
- Medium severity, with a CVSS score of 4, published 14 May 2026.
- Which products and versions are affected?
- openssl (crates.io) SEMVER:introduced=0.10.0,fixed=0.10.79.
- Is there a fix for CVE-2026-44662?
- Yes. openssl (crates.io): upgrade to 0.10.79 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44662 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-44662?
- Check whether you run openssl (crates.io) 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.79 or later
cargo update -p openssl
Technical details
A heap-based buffer overflow exists in rust-openssl's CipherCtxRef::cipher_update, CipherCtxRef::cipher_update_vec, and symm::Crypter::update functions. The root cause is an incorrect calculation of the required output buffer size when using AES key-wrap-with-padding ciphers (EVP_aes_{128,192,256}_wrap_pad). If the input length is not a multiple of 8 bytes, the underlying OpenSSL implementation may write up to 7 bytes beyond the allocated buffer. An attacker who can influence the length of the plaintext being encrypted can trigger this overflow to cause heap corruption. The vulnerability is fixed in version 0.10.79.
Affected products
- rust-openssl openssl (rust-openssl) >= 0.10.0, < 0.10.79
Identifiers
- CVE-2026-44662
- GHSA-xv59-967r-8726
- RUSTSEC-2026-0476
Timeline
- 2026-05-04: disclosed: Initial disclosure by maintainers
- 2026-05-07: advisory: GitHub Advisory published
- 2026-05-14: advisory: NVD entry published