Skip to content
Noroxi
CVE-2025-69418· NVD / CVE Program· CNA openssl

Unauthenticated/unencrypted trailing bytes with low-level OCB function calls

Noroxi assessment

Priority: Monitor (action score 16/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: OpenSSL OpenSSL 3.0.19, 3.3.6, 3.4.4; azl3 openvmm 0.2.0-1 on Azure Linux 3.0 Release Notes.

Low priority for now. Upgrade to OpenSSL OpenSSL 3.0.19, 3.3.6, 3.4.4; azl3 openvmm 0.2.0-1 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 4.0 · v3.1—No exploit Fix available
Published
Jan 27, 2026
Updated
Oct 15, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

16

Monitor

Low priority for now.

CVSS
16 / 40 · 4.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-69418

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for openssl records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
opensslopenssl

Check your server's TLS configuration

The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.

Run the SSL check

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • openssl openssl1.1.1 and later · before 1.1.1ze
  • openssl openssl3.0.0 and later · before 3.0.19
  • openssl openssl3.3.0 and later · before 3.3.6
  • openssl openssl3.4.0 and later · before 3.4.4
  • openssl openssl3.5.0 and later · before 3.5.5
  • openssl openssl3.6.0 and later · before 3.6.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.

  • OpenSSL OpenSSL

    • 3.6.0 and later · before 3.6.1affected · semver
    • 3.5.0 and later · before 3.5.5affected · semver
    • 3.4.0 and later · before 3.4.4affected · semver
    • 3.3.0 and later · before 3.3.6affected · semver
    • 3.0.0 and later · before 3.0.19affected · semver
    • 1.1.1 and later · before 1.1.1zeaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10opensslbefore 1:3.5.1-7.el10_1.alma.11:3.5.1-7.el10_1.alma.1
AlmaLinux:10openssl-develbefore 1:3.5.1-7.el10_1.alma.11:3.5.1-7.el10_1.alma.1
AlmaLinux:10openssl-libsbefore 1:3.5.1-7.el10_1.alma.11:3.5.1-7.el10_1.alma.1
AlmaLinux:10openssl-perlbefore 1:3.5.1-7.el10_1.alma.11:3.5.1-7.el10_1.alma.1
AlmaLinux:9opensslbefore 1:3.5.1-7.el9_71:3.5.1-7.el9_7
AlmaLinux:9openssl-develbefore 1:3.5.1-7.el9_71:3.5.1-7.el9_7
AlmaLinux:9openssl-libsbefore 1:3.5.1-7.el9_71:3.5.1-7.el9_7
AlmaLinux:9openssl-perlbefore 1:3.5.1-7.el9_71:3.5.1-7.el9_7
Alpine:v3.17opensslfrom 1.1.1 · before 3.0.19-r03.0.19-r0
Alpine:v3.20opensslfrom 1.1.1 · before 3.3.6-r03.3.6-r0
Alpine:v3.22opensslfrom 1.1.1 · before 3.5.5-r03.5.5-r0
Debian:11opensslbefore 1.1.1w-0+deb11u51.1.1w-0+deb11u5
Debian:12opensslbefore 3.0.18-1~deb12u23.0.18-1~deb12u2
Debian:13opensslbefore 3.5.4-1~deb13u23.5.4-1~deb13u2
Debian:14opensslbefore 3.5.5-13.5.5-1
openSUSE:Leap 15.6openssl-1_1before 1.1.1w-150600.5.21.11.1.1w-150600.5.21.1
openSUSE:Leap 15.6openssl-3before 3.1.4-150600.5.42.13.1.4-150600.5.42.1
openSUSE:Leap 16.0openssl-3before 3.5.0-160000.5.13.5.0-160000.5.1
openSUSE:Tumbleweedopenssl-3before 3.5.3-2.13.5.3-2.1
Red Hat:enterprise_linux_eus:10.0opensslbefore 1:3.2.2-16.el10_0.71:3.2.2-16.el10_0.7
Red Hat:enterprise_linux_eus:10.0openssl-debuginfobefore 1:3.2.2-16.el10_0.71:3.2.2-16.el10_0.7
Red Hat:enterprise_linux_eus:10.0openssl-debugsourcebefore 1:3.2.2-16.el10_0.71:3.2.2-16.el10_0.7
Red Hat:enterprise_linux_eus:10.0openssl-develbefore 1:3.2.2-16.el10_0.71:3.2.2-16.el10_0.7
Red Hat:enterprise_linux_eus:10.0openssl-libsbefore 1:3.2.2-16.el10_0.71:3.2.2-16.el10_0.7

+51

Same product

openssl: all records

Other highest-scoring records for the same primary product.

  • CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remKEV
    90Now
  • CVE-2021-3711SM2 Decryption Buffer Overflow
    65This week
  • CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code
    65This week

Published before and after this one in the same product

  • ← EarlierCVE-2025-66199Jan 27, 2026 · TLS 1.3 CompressedCertificate excessive memory allocation
    23Monitor
  • ← EarlierCVE-2025-68160Jan 27, 2026 · Heap out-of-bounds write in BIO_f_linebuffer on short writes
    18Monitor
  • Later →CVE-2025-69419Jan 27, 2026 · Out of bounds write in PKCS12_get_friendlyname() UTF-8 conversion
    29Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
OpenSSL OpenSSL3.0.19Vendor (CNA)
OpenSSL OpenSSL3.3.6Vendor (CNA)
OpenSSL OpenSSL3.4.4Vendor (CNA)
OpenSSL OpenSSL3.5.5Vendor (CNA)
OpenSSL OpenSSL3.6.1Vendor (CNA)
azl3 openvmm 0.2.0-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
almalinux:openssl1:3.5.1-7.el10_1.alma.1 · AlmaLinux:10Package registry (OSV)
almalinux:openssl-devel1:3.5.1-7.el10_1.alma.1 · AlmaLinux:10Package registry (OSV)
almalinux:openssl-libs1:3.5.1-7.el10_1.alma.1 · AlmaLinux:10Package registry (OSV)
almalinux:openssl-perl1:3.5.1-7.el10_1.alma.1 · AlmaLinux:10Package registry (OSV)
alpine:openssl3.0.19-r0 · Alpine:v3.17Package registry (OSV)
debian:openssl3.0.18-1~deb12u2 · Debian:12Package registry (OSV)
opensuse:openssl-1_11.1.1w-150600.5.21.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:openssl-33.1.4-150600.5.42.1 · openSUSE:Leap 15.6Package registry (OSV)
red hat:openssl1:3.5.1-7.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:openssl-config-fips0:3.5.6-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:openssl-debuginfo1:3.5.1-7.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:openssl-debugsource1:3.5.1-7.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:openssl-devel1:3.5.1-7.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:openssl-devel-engine0:3.5.6-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:openssl-libs1:3.5.1-7.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:openssl-libs-debuginfo1:3.5.1-7.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:openssl-perl1:3.5.1-7.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
rocky linux:openssl1:3.5.1-7.el10_1 · Rocky Linux:10Package registry (OSV)
suse:openssl-1_11.1.1w-150600.5.21.1 · SUSE:Linux Enterprise Server 15 SP6-LTSSPackage registry (OSV)
suse:openssl-1_11.1.1w-150700.11.11.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:openssl-33.1.4-150600.5.42.1 · SUSE:Linux Enterprise Server 15 SP6-LTSSPackage registry (OSV)
suse:openssl-33.2.3-150700.5.24.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-45445133 days apartAES-OCB IV Ignored on EVP_Cipher() Path
    30Monitor
  • CVE-2026-45446133 days apartIncorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes
    19Monitor
  • CVE-2026-42770133 days apartFFC-DH Peer Validation Uses Attacker-Supplied q
    14Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Local
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-325 · Missing Cryptographic Step

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records