OpenSSL · OpenSSL · published 2026-01-27

CVE-2025-15469'openssl dgst' one-shot codepath silently truncates inputs >16MB

Routine No exploitation evidence; EPSS 0.2%.

CVE-2025-15469 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 11% of all CVEs. This OpenSSL vulnerability: CVSS 5.5 (v3.1). Fixed upstream in OpenSSL 3.6.1, 3.5.5, 3.4.4, 3.3.6 (+3 more). Routine: patch when convenient.

Share this

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

  1. This weekSecurity release

    Crypto libraryOpenSSL

    OpenSSL security fixes: 12 CVEs

    Upgrade to 3.6.13.5.53.4.43.3.63.0.191.1.1ze1.0.2zn

    Why: CVE-2025-15467: EPSS 75% chance of exploitation in 30 days, with critical impact.

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (12th pct)FIRST EPSS v2026.06.15
CVSS base score5.5 (v3.1)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

Issue summary: The 'openssl dgst' command-line tool silently truncates input data to 16MB when using one-shot signing algorithms and reports success instead of an error. Impact summary: A user signing or verifying files larger than 16MB with one-shot algorithms (such as Ed25519, Ed448, or ML-DSA) may believe the entire file is authenticated while trailing data beyond 16MB remains unauthenticated. When the 'openssl dgst' command is used with algorithms that only support one-shot signing (Ed25519, Ed448, ML-DSA-44, ML-DSA-65, ML-DSA-87), the input is buffered with a 16MB limit. If the input exceeds this limit, the tool silently truncates to the first 16MB and continues without signaling an error, contrary to what the documentation states. This creates an integrity gap where trailing bytes can be modified without detection if both signing and verification are performed using the same affected codepath. The issue affects only the command-line tool behavior. Verifiers that process the full message using library APIs will reject the signature, so the risk primarily affects workflows that both sign and verify with the affected 'openssl dgst' command. Streaming digest algorithms for 'openssl dgst' and library users are unaffected. The FIPS modules in 3.5 and 3.6 are not affected by this issue, as the command-line tools are outside the OpenSSL FIPS module boundary. OpenSSL 3.5 and 3.6 are vulnerable to this issue. OpenSSL 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →