Vulnerability · CVE-2025-15469
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.
Published Jan 27, 2026 · catalog updated Jun 17, 2026 · Issue summary: The 'openssl
Last checked Nov 4, 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-15469. EPSS is 0.21%. Act only if a listed version of Issue summary: The 'openssl 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: The 'openssl).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-84783 · High
- CVE-2026-84782 · High
- CVE-2026-77696 · Low
- CVE-2026-75806 · Medium
- CVE-2026-75805 · Medium
- Severity
- Medium5.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.21%
- Remediation
- Version ranges on file
- Affected products
- cpe openssl/openssl · vendor OpenSSL OpenSSL 3.5.0 <3.5.5
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.
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< 3.5.5
- cpe openssl/openssl< 3.6.1
- vendor OpenSSL OpenSSL 3.5.0 <3.5.53.5.0 <3.5.5
How to fix CVE-2025-15469
Upgrade
CVE-2025-15469 lists a fix boundary at 3.5.5. Compare the installed build with that boundary before you change production.
Version check
Affected < 3.5.5
Advisory
Open the cve_org record and follow its fix.
Official advisories
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-15469. EPSS is 0.21%. Act only if a listed version of Issue summary: The 'openssl is installed.
Which versions are affected?
Compare what you have installed with OpenSSL OpenSSL 3.5.0 <3.5.5 3.5.0 <3.5.5. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-347: Improper Verification of Cryptographic Signature. EPSS 0.21%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Jan 27, 2026 · EUVD
Detected
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.
Jan 29, 2026 · EUVD
Updated
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.
Jun 17, 2026 · Monitored products — critical
Updated
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.
Sources
- CVE.orgVulnerability recordCVE-2025-15469
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2025-15469
30-day exploitation probability 0.21%
first.org - EUVDVulnerability recordEUVD-2025-206399
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,
euvd.enisa.europa.eu - Monitored products — criticalVendor advisoryCVE-2025-15469
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.
nvd.nist.gov
References
Freshness
Last verified in this catalog Nov 4, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- Monitored products — criticalNov 4, 2026
- FIRST EPSSNov 4, 2026
- CVE.orgNov 4, 2026
- EUVDNov 4, 2026