Skip to main content
Mallory
MediumVulnerability

CVE-2025-69418: Incomplete encryption and authentication in OpenSSL low-level OCB APIs

Published Jan 27, 2026 · Updated 10 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 4 in a dayToday
CVSS4.0Medium · v3.1
EPSS0.13%3rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
OpenSSL Software Foundation
IdentifiersCVE-2025-69418CWE-325 · Missing Cryptographic Step

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
OpenSSL Software FoundationOpensslapplication
FAQ

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.
Activity feed

Recent activity

57 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.0 : openssl (EulerOS-SA-2026-4609) | Tenable®Direct calls to OpenSSL's hardware-accelerated CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() with non-block-aligned input can leave the final 1–15 bytes exposed and unauthenticated, enabling undetected disclosure or tampering. Typical EVP consumers are unaffected because full blocks and partial blocks are processed separately. TLS does not use OCB cipher suites.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.1 : edk2 (EulerOS-SA-2026-4683) | Tenable®OpenSSL's hardware-accelerated low-level OCB routines mishandle trailing partial blocks, potentially exposing the last 1–15 bytes in cleartext and allowing undetected modification. The flaw affects direct calls to CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() with non-block-aligned input. Typical EVP consumers, TLS and FIPS modules are unaffected. The advisory assesses the issue as Low severity.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.1 : openssl (EulerOS-SA-2026-4567) | Tenable®Incorrect pointer handling in hardware-accelerated low-level OCB processing leaves the final 1–15 bytes of non-block-aligned input unencrypted and unauthenticated, allowing disclosure or undetected modification. Normal EVP consumers avoid the vulnerable path, TLS does not use OCB, and FIPS modules are unaffected. The advisory rates this issue Low severity.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.0 : edk2 (EulerOS-SA-2026-4741) | Tenable®OpenSSL's hardware-accelerated low-level OCB routines mishandle pointers when processing full blocks followed by a partial block in one call. The final 1–15 bytes can remain in cleartext and outside authentication coverage, allowing disclosure or undetected modification. Applications using the higher-level EVP/provider implementation avoid the vulnerable path because full and partial blocks are processed separately. TLS does not use OCB. The advisory assesses severity as Low; OpenSSL 1.0.2 and FIPS modules are unaffected. Exploit availability is reported only at the aggregate plugin level.Read more ↗
+29 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity15Community discussion across Reddit, Mastodon, and other social sources.