dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2026-44662

MEDIUM · 5.1 CVSS v4.0 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The rust-openssl library contains a buffer overflow vulnerability in CipherCtxRef::cipher_update, CipherCtxRef::cipher_update_vec, and symm::Crypter::update when using AES key-wrap-with-padding ciphers (EVP_aes_{128,192,256}_wrap_pad). For non-multiple-of-8 byte inputs, OpenSSL writes up to 7 bytes past the end of the caller's buffer, leading to heap corruption when plaintext length is attacker-controlled.

MitigationUpgrade rust-openssl to version 0.10.79 or later. If immediate upgrade is not feasible, avoid using AES key-wrap-with-padding ciphers until the patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify rust-openssl version in use
    Check Cargo.lock for the rust-openssl crate version, or run 'cargo tree -p openssl' to see the exact version
    Affected if Version is lower than 0.10.79
  2. Check for AES key-wrap-with-padding cipher usage
    Search source code for calls to EVP_aes_128_wrap_pad, EVP_aes_192_wrap_pad, EVP_aes_256_wrap_pad, or Rust equivalents like cipher::Aes128WrapPad
    Affected if Code uses any of the AES wrap_pad cipher variants
  3. Verify input length handling
    Review code paths that pass data to the wrap_pad ciphers to determine if input lengths can be controlled externally
    Affected if Input lengths to wrap_pad operations can be controlled by an attacker and are not guaranteed to be multiples of 8 bytes
  4. Confirm Crypter or CipherCtxRef usage with wrap_pad
    Search for usage of symm::Crypter::update or CipherCtxRef::cipher_update/cipher_update_vec with wrap_pad ciphers
    Affected if These methods are called with AES key-wrap-with-padding ciphers on user-controlled data

A user is affected if their rust-openssl version is below 0.10.79 AND their code uses AES key-wrap-with-padding ciphers (EVP_aes_*_wrap_pad) with attacker-influenced input lengths that are not multiples of 8 bytes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade rust-openssl to version 0.10.79 or later. If immediate upgrade is not feasible, avoid using AES key-wrap-with-padding ciphers until the patch can be applied.

Recommended fix High confidence

rust-openssl version 0.10.79 or later

  1. Locate your Cargo.toml file that depends on the rust-openssl crate
  2. Update the rust-openssl dependency version to 0.10.79 or later
  3. Run cargo update to update the lockfile
  4. Rebuild your project with cargo build to verify the fix compiles successfully
  5. If using AES key-wrap-with-padding ciphers (EVP_aes_128_wrap_pad, EVP_aes_192_wrap_pad, or EVP_aes_256_wrap_pad), verify your application works correctly with the updated library

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44662 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44662 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data