CVE-2026-44662Medium

Microsoft security update for CVE-2026-44662 — azl4

Published
May 22, 2026
Last Modified
—

🔗 CVE IDs covered (1)

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-44662. This page also shows what EchelonGraph holds for CVE-2026-44662, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products4

  • azl4 389-ds-base 3.1.5-5.azl4 on Azure Linux 4.0
  • azl4 fido-device-onboard 0.5.5-13.azl4 on Azure Linux 4.0
  • azl4 rpm-ostree 2026.1-7.azl4 on Azure Linux 4.0
  • azl4 rust 1.99.0-2.azl4 on Azure Linux 4.0

✅ Updates Microsoft lists: 1 update

1 row: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update—

🧭 EchelonGraph on CVE-2026-44662

EchelonGraph score
5.1 MEDIUM
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

rust-openssl provides OpenSSL bindings for the Rust programming language. From 0.10.0 to before 0.10.79, CipherCtxRef::cipher_update, CipherCtxRef::cipher_update_vec, and symm::Crypter::update incorrectly sized output buffers when used with AES key-wrap-with-padding ciphers (EVP_aes_{128,192,256}_wrap_pad). For a non-multiple-of-8 input, OpenSSL writes up to 7 bytes past the end of the caller's buffer or Vec, producing attacker-controllable heap corruption when the plaintext length is attacker-influenced. This only impacts users using AES key-wrap-with-padding ciphers. This vulnerability is fixed in 0.10.79.

Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2026-44662, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (2)