CVE-2025-69418: Incomplete encryption and authentication in OpenSSL low-level OCB APIs
- Vendor
- OpenSSL Software Foundation
CVE-2025-69418 is a cryptographic processing flaw in OpenSSL's low-level CRYPTO_ocb128_encrypt() and CRYPTO_ocb128_decrypt() routines on AES-NI and other hardware-accelerated code paths. The accelerated stream path processes full 16-byte blocks without advancing the input and output pointers. Subsequent partial-block handling therefore reprocesses the beginning of the buffer instead of the actual tail, potentially leaving the final 1–15 bytes unencrypted and excluded from the authentication checksum. Vulnerable release branches include OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, and 1.1.1. OpenSSL 1.0.2 is unaffected. Higher-level EVP and provider OCB implementations avoid the faulty path by processing full blocks and partial tails separately. TLS does not use OCB cipher suites, and OpenSSL FIPS modules are unaffected because OCB is not FIPS-approved.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Affected applications can lose confidentiality and integrity protection for the final 1–15 bytes of a message. Encryption may expose these bytes in cleartext, while their exclusion from the authentication checksum permits modification without detection by the OCB authentication tag. The issue is assessed as Low severity because it requires a narrowly defined direct low-level API usage pattern; typical EVP consumers and TLS are unaffected.
Mitigation
If you can’t patch tonight, do this now.
Prefer the higher-level EVP/provider OCB interfaces instead of direct low-level OCB calls. If low-level interfaces must be retained, process the complete 16-byte blocks and final partial block in separate calls rather than submitting a non-block-aligned buffer containing both in one call.
Remediation
Patch, then assume compromise.
Install an OpenSSL security update that fixes CVE-2025-69418. Fixed releases include 3.6.1, 3.5.5, 3.4.4, 3.3.6, and 3.0.19 for their respective branches; distribution-maintained installations should use the corresponding vendor-patched packages. Update affected bundled copies through the containing product's security release. A fixed OpenSSL 1.1.1 release number is not specified.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2025-69418 exploited in the wild?
- As of Nov 7, 2026, Mallory has no reports of CVE-2025-69418 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2025-69418?
- As of Nov 7, 2026, Mallory has found no public exploit for CVE-2025-69418.
- Is there a patch for CVE-2025-69418?
- Install an OpenSSL security update that fixes CVE-2025-69418. Fixed releases include 3.6.1, 3.5.5, 3.4.4, 3.3.6, and 3.0.19 for their respective branches; distribution-maintained installations should use the corresponding vendor-patched packages.
- What products are affected by CVE-2025-69418?
- OpenSSL Software Foundation Openssl.
- How severe is CVE-2025-69418?
- CVE-2025-69418 has a CVSS v3.1 score of 4.0 (Medium) and an EPSS score of 0.13% (3rd percentile) as of Nov 7, 2026.
Recent activity
57 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.