ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-69418

Issue summary: When using the low-level OCB API directly with AES-NI or other hardware-accelerated code paths, inputs whose length is not a multiple of 16 bytes can leave the final

Published Jan 27, 2026 · catalog updated Oct 15, 2026 · Issue summary: When using

Last checked Nov 5, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2025-69418. EPSS is 0.13%. Act only if a listed version of Issue summary: When using is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Issue summary: When using).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
Medium4.0
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.13%
Remediation
Version ranges on file
Affected products
cpe openssl/openssl · vendor OpenSSL OpenSSL 3.3.0 <3.3.6

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

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe openssl/openssl< 1.1.1ze
  • cpe openssl/openssl< 3.0.19
  • cpe openssl/openssl< 3.3.6
  • cpe openssl/openssl< 3.4.4
  • cpe openssl/openssl< 3.5.5
  • cpe openssl/openssl< 3.6.1
  • vendor OpenSSL OpenSSL 3.3.0 <3.3.63.3.0 <3.3.6

How to fix CVE-2025-69418

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-69418. EPSS is 0.13%. Act only if a listed version of Issue summary: When using is installed.

Which versions are affected?

Compare what you have installed with OpenSSL OpenSSL 3.3.0 <3.3.6 3.3.0 <3.3.6. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-325. EPSS 0.13%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

OpenSSL security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jan 27, 2026 · EUVD

    Detected

    Issue summary: When using the low-level OCB API directly with AES-NI or other hardware-accelerated code paths, inputs whose length is not a multiple of 16 bytes can leave the final partial block unencrypted and unauthenticated. Impact summary: The trailing 1-15 bytes of a message may be exposed in cleartext on encryption and are not covered by the authentication tag, allowing an attacker to read o

  2. Oct 15, 2026 · EUVD

    Updated

    Issue summary: When using the low-level OCB API directly with AES-NI or other hardware-accelerated code paths, inputs whose length is not a multiple of 16 bytes can leave the final partial block unencrypted and unauthenticated. Impact summary: The trailing 1-15 bytes of a message may be exposed in cleartext on encryption and are not covered by the authentication tag, allowing an attacker to read o

Sources

  • CVE.orgVulnerability recordCVE-2025-69418

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-69418

    30-day exploitation probability 0.13%

    first.org
  • EUVDVulnerability recordEUVD-2025-206396

    Issue summary: When using the low-level OCB API directly with AES-NI or other hardware-accelerated code paths, inputs whose length is not a multiple of 16 bytes can leave the final partial block unencrypted and unauthenticated. Impact summary: The trailing 1-15 bytes of a message

    euvd.enisa.europa.eu
  • Monitored products — criticalVendor advisoryCVE-2025-69418

    Issue summary: When using the low-level OCB API directly with AES-NI or other hardware-accelerated code paths, inputs whose length is not a multiple of 16 bytes can leave the final partial block unencrypted and unauthenticated. Impact summary: The trailing 1-15 bytes of a message may be exposed in cleartext on encryption and are not covered by the authentication tag, allowing an attacker to read o

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 5, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSNov 5, 2026
  • Monitored products — criticalNov 4, 2026
  • CVE.orgNov 4, 2026
  • EUVDNov 2, 2026