4.0
MEDIUM CVSS 3.1
CVE-2025-69418
Unauthenticated/unencrypted trailing bytes with low-level OCB function calls
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.

INFO

Published Date :

Jan. 27, 2026, 4:16 p.m.

Last Modified :

Feb. 2, 2026, 6:36 p.m.

Remotely Exploit :

No
Affected Products

The following products are affected by CVE-2025-69418 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Openssl openssl
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 MEDIUM 134c704f-9b21-4f2e-91b3-4a467353bcc0
Solution
Applications directly calling low-level OCB API with non-block-aligned lengths are vulnerable. Update to a patched version.
  • Update OpenSSL to a patched version.
  • Avoid direct calls to CRYPTO_ocb128_encrypt/decrypt.
  • Use higher-level EVP API for OCB encryption.
  • Ensure partial blocks are handled correctly.
Public PoC/Exploit Available at Github

CVE-2025-69418 has a 2 public PoC/Exploit available at Github. Go to the Public Exploits tab to see the list.

CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2025-69418 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2025-69418 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Scripts, gists, and current projects

Updated: 2 weeks ago
1 stars 0 fork 0 watcher
Born at : Jan. 17, 2026, 2:51 p.m. This repo has been linked 4 different CVEs too.

使用Google Gemini API,对hacker news Top100文章总结摘要并翻译成体中文,每日自动更新。

ai gemini hacker-news hackernews summarizer

Ruby Shell Python

Updated: 2 weeks, 6 days ago
8 stars 2 fork 2 watcher
Born at : March 19, 2025, 11:57 a.m. This repo has been linked 8 different CVEs too.

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2025-69418 vulnerability anywhere in the article.

  • CybersecurityNews
OpenSSL Vulnerabilities Allow Remote Attackers to Execute Malicious Code

OpenSSL patched 12 vulnerabilities on January 27, 2026, including one high-severity flaw that could lead to remote code execution. Most issues cause denial-of-service attacks but highlight risks in pa ... Read more

Published Date: Jan 28, 2026 (2 weeks, 5 days ago)

The following table lists the changes that have been made to the CVE-2025-69418 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • Initial Analysis by [email protected]

    Feb. 02, 2026

    Action Type Old Value New Value
    Added CPE Configuration OR *cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 3.0.0 up to (excluding) 3.0.19 *cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 3.3.0 up to (excluding) 3.3.6 *cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 3.4.0 up to (excluding) 3.4.4 *cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 3.5.0 up to (excluding) 3.5.5 *cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 3.6.0 up to (excluding) 3.6.1 *cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 1.1.1 up to (excluding) 1.1.1ze
    Added Reference Type OpenSSL Software Foundation: https://github.com/openssl/openssl/commit/372fc5c77529695b05b4f5b5187691a57ef5dffc Types: Patch
    Added Reference Type OpenSSL Software Foundation: https://github.com/openssl/openssl/commit/4016975d4469cd6b94927c607f7c511385f928d8 Types: Patch
    Added Reference Type OpenSSL Software Foundation: https://github.com/openssl/openssl/commit/52d23c86a54adab5ee9f80e48b242b52c4cc2347 Types: Patch
    Added Reference Type OpenSSL Software Foundation: https://github.com/openssl/openssl/commit/a7589230356d908c0eca4b969ec4f62106f4f5ae Types: Patch
    Added Reference Type OpenSSL Software Foundation: https://github.com/openssl/openssl/commit/ed40856d7d4ba6cb42779b6770666a65f19cb977 Types: Patch
    Added Reference Type OpenSSL Software Foundation: https://openssl-library.org/news/secadv/20260127.txt Types: Vendor Advisory
  • CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0

    Jan. 29, 2026

    Action Type Old Value New Value
    Added CVSS V3.1 AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
  • New CVE Received by [email protected]

    Jan. 27, 2026

    Action Type Old Value New Value
    Added 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.
    Added CWE CWE-325
    Added Reference https://github.com/openssl/openssl/commit/372fc5c77529695b05b4f5b5187691a57ef5dffc
    Added Reference https://github.com/openssl/openssl/commit/4016975d4469cd6b94927c607f7c511385f928d8
    Added Reference https://github.com/openssl/openssl/commit/52d23c86a54adab5ee9f80e48b242b52c4cc2347
    Added Reference https://github.com/openssl/openssl/commit/a7589230356d908c0eca4b969ec4f62106f4f5ae
    Added Reference https://github.com/openssl/openssl/commit/ed40856d7d4ba6cb42779b6770666a65f19cb977
    Added Reference https://openssl-library.org/news/secadv/20260127.txt
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
Base CVSS Score: 4.0
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality Impact
Integrity Impact
Availability Impact