Answer in brief
CVE-2026-44662 records a Unknown severity vulnerability in rust-openssl vulnerable to heap buffer overflow when encrypting with AES key-wrap-with-padding. The current sources do not mark it as known exploited. The current feed maps openssl (crates.io). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps openssl (crates.io). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| opensslcrates.io | >=0.10.0 <0.10.79 | 0.10.79 |
Published upstream
May 4, 2026
Evidence: source:osv:source_dates:source-dates:recordSource modified
Nov 10, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Nov 10, 2026
`CipherCtxRef::cipher_update`, `CipherCtxRef::cipher_update_vec` and `symm::Crypter::update` require (or allocate) `input.len() + block_size` bytes of output. With the AES key-wrap-with-padding ciphers (`EVP_aes_128_wrap_pad`, `EVP_aes_192_wrap_pad`, `EVP_aes_256_wrap_pad`), OpenSSL pads the input to a multiple of 8 bytes and adds an 8-byte block, so when the input length is not a multiple of 8 it writes up to 7 bytes past the end of the caller's buffer or `Vec`. If an attacker can influence the plaintext length, this is heap corruption they can partly control. Only users of the AES key-wrap-with-padding ciphers are affected. 0.10.79 sizes the output for these ciphers as the input length rounded up to a multiple of 8, plus 8.
Quoted source text, attributed separately from HOL analysis.