# CVE-2025-69418: Unauthenticated/unencrypted trailing bytes with low-level OCB function calls

> Direct low-level OCB API calls on hardware-accelerated builds may leave trailing bytes unencrypted and unauthenticated, exposing data to attackers.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A: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:** 27 Jan 2026
- **Updated:** 15 Oct 2026
- **Also known as:** ALPINE-CVE-2025-69418, AZL-75272, AZL-75783, AZL-75899, AZL-76128, AZL-76158, AZL-76200, AZL-78546, BELL-CVE-2025-69418, DEBIAN-CVE-2025-69418, ECHO-2c1d-6266-fce5, GHSA-78qr-24v5-7q73, JLSEC-2026-262, MINI-4fp7-99hp-c5m2, MINI-qg2w-mv6w-hjxw, MINI-x6h8-hw8q-62mp, OESA-2026-1613, OESA-2026-1663, ROOT-OS-ALPINE-317-CVE-2025-69418, UBUNTU-CVE-2025-69418

## What is CVE-2025-69418?

CVE-2025-69418 is a medium-severity vulnerability in Openssl Openssl, published on 27 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Issue summary: When using the low-level OCB API directly with AES-NI or<br>other hardware-accelerated code paths, inputs whose length is not a multiple<br>of 16 bytes can leave the final partial block unencrypted and unauthenticated.<br><br>Impact summary: The trailing 1-15 bytes of a message may be exposed in<br>cleartext on encryption and are not covered by the authentication tag,<br>allowing an attacker to read or tamper with those bytes without detection.<br><br>The low-level OCB encrypt and decrypt routines in the hardware-accelerated<br>stream path process full 16-byte blocks but do not advance the input/output<br>pointers. The subsequent tail-handling code then operates on the original<br>base pointers, effectively reprocessing the beginning of the buffer while<br>leaving the actual trailing bytes unprocessed. The authentication checksum<br>also excludes the true tail bytes.<br><br>However, typical OpenSSL consumers using EVP are not affected because the<br>higher-level EVP and provider OCB implementations split inputs so that full<br>blocks and trailing partial blocks are processed in separate calls, avoiding<br>the problematic code path. Additionally, TLS does not use OCB ciphersuites.<br>The vulnerability only affects applications that call the low-level<br>CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with<br>non-block-aligned lengths in a single call on hardware-accelerated builds.<br>For these reasons the issue was assessed as Low severity.<br><br>The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected<br>by this issue, as OCB mode is not a FIPS-approved algorithm.<br><br>OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.<br><br>OpenSSL 1.0.2 is not affected by this issue.

Weakness: CWE-325 (Missing Cryptographic Step)

## Which versions are affected by CVE-2025-69418?

It affects 1 product.


Products: Openssl Openssl.

## How do I fix CVE-2025-69418?

Apply the vendor's patch.

## Is CVE-2025-69418 being exploited?

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

## Other vulnerabilities in Openssl Openssl

- [CVE-2009-3245](https://insights.sbomify.com/CVE-2009-3245/): Null dereference in n/a (critical 10.0)
- [CVE-2006-3738](https://insights.sbomify.com/CVE-2006-3738/): Memory corruption in n/a (critical 10.0)
- [CVE-2026-63073](https://insights.sbomify.com/CVE-2026-63073/): Untrusted Sender DN Used as Format String in CMP Response Validation (critical 9.8)
- [CVE-2016-6309](https://insights.sbomify.com/CVE-2016-6309/): Use after free in n/a (critical 9.8)
- [CVE-2016-0799](https://insights.sbomify.com/CVE-2016-0799/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-69418 and fix it if it is affected.

What it is: CVE-2025-69418 is a medium-severity vulnerability in Openssl Openssl, published on 27 Jan 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-2025-69418 in the wild and no public exploit code.

Affected product: Openssl Openssl. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2025-69418/ (Markdown: https://insights.sbomify.com/CVE-2025-69418/index.md)
```

## Sources

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

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