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

> An out-of-bounds write in rust-openssl allows attackers to cause heap corruption and potentially execute code via crafted AES-KW-PAD inputs.

- **Severity:** Medium 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** AZL-92456, DEBIAN-CVE-2026-45784, GHSA-phqj-4mhp-q6mq, MINI-2x6v-9q8v-x9j9, MINI-7xf8-vj97-53x3, MINI-9j34-wmq5-qx94, MINI-c3m8-vm7h-xrg9, MINI-c88c-8w38-mmpv, MINI-mg44-64p8-j5rm, MINI-q467-w74p-5xgf, MINI-w842-cj3w-6h85, MINI-xqgx-xh9r-qcwr, SUSE-SU-2026:23233-1, UBUNTU-CVE-2026-45784, openSUSE-SU-2026:21573-1

## What is CVE-2026-45784?

CVE-2026-45784 is a medium-severity memory corruption vulnerability in rust-openssl, published on 17 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write), CWE-131 (Incorrect Calculation of Buffer Size)

## Which versions are affected by CVE-2026-45784?

2 open source packages ship an affected version, including openssl. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openssl` | crates.io | From 0.10.50 | 0.10.80 |
| `openssl` | crates.io | From 0.10.50 | 0.10.80 |
| `himmelblau` | SUSE:Linux Enterprise Server 16.0 | All versions | 2.3.14+git0.e23b4c54-160000.1.1 |
| `himmelblau` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 2.3.14+git0.e23b4c54-160000.1.1 |
| `himmelblau` | openSUSE:Leap 16.0 | All versions | 2.3.14+git0.e23b4c54-160000.1.1 |

Products: Sfackler Openssl.

## How do I fix CVE-2026-45784?

Upgrade openssl to 0.10.80 or later.

## Is CVE-2026-45784 being exploited?

There is no known exploitation of CVE-2026-45784 in the wild and no public exploit code.

## Other vulnerabilities in rust-openssl

- [CVE-2023-53159](https://insights.sbomify.com/CVE-2023-53159/): `openssl` `X509VerifyParamRef::set_host` buffer over-read (medium 4.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45784 and fix it if it is affected.

What it is: CVE-2026-45784 is a medium-severity memory corruption vulnerability in rust-openssl, published on 17 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-45784 in the wild and no public exploit code.

Affected packages and fixed versions:
- openssl (crates.io): affected from 0.10.50; fixed in 0.10.80
- openssl (crates.io): affected from 0.10.50; fixed in 0.10.80

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45784/ (Markdown: https://insights.sbomify.com/CVE-2026-45784/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45784
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45784
- OSV: https://osv.dev/vulnerability/CVE-2026-45784

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45784/
Summaries are generated and may contain mistakes; the official description above is the record.