OpenSSL · OpenSSL · published 2026-01-27
CVE-2025-69418Unauthenticated/unencrypted trailing bytes with low-level OCB function calls
Routine No exploitation evidence; EPSS 0.1%.
CVE-2025-69418 is not known to be exploited in the wild. EPSS estimates a 0.1% chance of exploitation in the next 30 days, higher than 2% of all CVEs. This OpenSSL vulnerability: CVSS 4.0 (v3.1). Fixed upstream in OpenSSL 3.6.1, 3.5.5, 3.4.4, 3.3.6 (+3 more). Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in OpenSSL 3.6.1, 3.5.5, 3.4.4, 3.3.6, 3.0.19, 1.1.1ze, 1.0.2zn.
Patch events
Crypto libraryOpenSSL
OpenSSL security fixes: 12 CVEs
Upgrade to
3.6.13.5.53.4.43.3.63.0.191.1.1ze1.0.2znWhy: CVE-2025-15467: EPSS 75% chance of exploitation in 30 days, with critical impact.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.1% (3th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 4.0 (v3.1)CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- OpenSSL OpenSSL
3.6.0to before3.6.1(affected)3.5.0to before3.5.5(affected)3.4.0to before3.4.4(affected)3.3.0to before3.3.6(affected)3.0.0to before3.0.19(affected)1.1.1to before1.1.1ze(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.