Skip to content
Fencer Intel
high 7.1

CVE-2026-45784 json

rust-openssl: Potential out-of-bounds write in `CipherCtxRef::cipher_update_inplace` for AES-KW-PAD ciphers

published 5mo ago modified last mo. also EUVD-2026-45322 , GHSA-phqj-4mhp-q6mq

cvss
7.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 2%
public exploits
0
none known

Summary

rust-openssl provides OpenSSL bindings for the Rust programming language. From 0.10.50 until 0.10.80, CipherCtxRef::cipher_update_inplace in openssl/src/cipher_ctx.rs 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 issue is fixed in version 0.10.80.

Patch / fix

  • crates.io openssl 0.10.80
  • rust-openssl_project rust-openssl 0.10.80
  • sfackler openssl 0.10.80
  • rust-openssl Debian 14 0.10.81-1

debian advisories DEBIAN-CVE-2026-45784

  • rustup SLES for SAP applications 16.0, SLES 16.0 1.29.1~0-160000.1.1
  • sccache SLES for SAP applications 16.0, SLES 16.0 0.18.0~2-160000.1.1
  • snpguest SLE Module for Server Applications 15 SP7 0.10.0-150700.3.6.1
  • snphost SLES for SAP applications 16.0, SLES 16.0 0.6.0-160000.3.1
  • snphost SLE Module for Confidential Computing Technical Preview 15 SP7 0.6.1-150700.3.6.1
  • snpguest SLES for SAP applications 16.0, SLES 16.0 0.10.0-160000.2.1
  • himmelblau SLES for SAP applications 16.0, SLES 16.0 2.3.14+git0.e23b4c54-160000.1.1
  • himmelblau SLES for SAP 15 SP6, SLES for SAP 15 SP5, SLES 15 SP6-LTSS +3 more 2.3.14+git0.e23b4c54-150500.11.12.1

suse advisories SUSE-SU-2026:24014-1SUSE-SU-2026:23983-1SUSE-SU-2026:3791-1SUSE-SU-2026:23327-1SUSE-SU-2026:3642-1SUSE-SU-2026:23236-1

  • rustup openSUSE Leap 16.0 1.29.1~0-160000.1.1
  • sccache openSUSE Leap 16.0 0.18.0~2-160000.1.1
  • sdbootutil openSUSE Leap 16.0 1+git20260908.c641fc2-160000.1.1
  • snpguest openSUSE Tumbleweed 0.10.0-3.1
  • snphost openSUSE Tumbleweed 0.7.0-3.1
  • snphost openSUSE Leap 16.0 0.6.0-160000.3.1
  • snpguest openSUSE Leap 16.0 0.10.0-160000.2.1
  • himmelblau openSUSE Leap 16.0 2.3.14+git0.e23b4c54-160000.1.1

opensuse advisories openSUSE-SU-2026:22016-1openSUSE-SU-2026:21982-1openSUSE-SU-2026:21933-1openSUSE-SU-2026:11653-1openSUSE-SU-2026:11654-1openSUSE-SU-2026:21638-1

Is CVE-2026-45784 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-45784 updated cvss 5.1

rust-openssl: rust-openssl: Heap Corruption from Incorrect Buffer Sizing

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
3mo ago

Exploit prediction

0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 4.0 5.1 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
CNA 4.0 5.1 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
NVD 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Affected packages

ecosystem package affected fixed in
crates.io openssl
>=0.10.50, <0.10.80
0.10.80

Affected products

  • rust-openssl rust-openssl

Classification

Weakness
  • CWE-131 Incorrect Calculation of Buffer Size
  • CWE-787 Out-of-bounds Write

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.