Skip to main content
Mallory
MediumVulnerability

CVE-2025-15469: OpenSSL dgst signature integrity bypass through silent input truncation

Published Jan 27, 2026 · Updated 12 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS5.5Medium · v3.1
EPSS0.21%12th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
OpenSSL Software Foundation
IdentifiersCVE-2025-15469CWE-347 · Improper Verification of…

CVE-2025-15469 is a silent input-truncation vulnerability in the OpenSSL dgst command-line tool affecting OpenSSL 3.5 before 3.5.5 and 3.6 before 3.6.1. When using one-shot signing algorithms Ed25519, Ed448, ML-DSA-44, ML-DSA-65, or ML-DSA-87, the tool buffers only the first 16 MiB of input and silently discards subsequent bytes while reporting success. When both signing and verification use this affected code path, trailing data is not authenticated and can be modified without invalidating verification. OpenSSL library APIs, streaming digest algorithms, and the OpenSSL 3.5 and 3.6 FIPS modules are unaffected. OpenSSL 3.4, 3.3, 3.0, 1.1.1, and 1.0.2 are not affected.

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 workflows may accept modified files as authentic because signature verification covers only the first 16 MiB rather than the complete input. An attacker can alter trailing data while retaining a successful verification result, compromising file integrity and authenticity. Verification through library APIs that process the entire message rejects signatures generated over the truncated input. No confidentiality loss, availability impact, or code execution is established for this vulnerability.

Mitigation

If you can’t patch tonight, do this now.

Do not sign or verify inputs larger than 16 MiB using the affected dgst one-shot algorithm path. Enforce an input-size limit that rejects oversized inputs rather than truncating them. For larger messages, use signing and verification implementations based on library APIs that process the complete message, or an appropriate unaffected streaming-signature workflow. Full-message verification will reject existing signatures that authenticate only a truncated prefix.

Remediation

Patch, then assume compromise.

Upgrade OpenSSL 3.5 installations to 3.5.5 or later, or OpenSSL 3.6 installations to 3.6.1 or later. Distribution-maintained installations can instead apply vendor packages containing the backported fix, including RHEL 9 package version 3.5.1-7.el9_7, RHEL 10 package version 3.5.1-7.el10_1, or Echo package version 3.5.0+e1 or later. Ensure signing and verification workflows invoke the patched command-line tool.

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-15469 exploited in the wild?
As of Nov 6, 2026, Mallory has no reports of CVE-2025-15469 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-15469?
As of Nov 6, 2026, Mallory has found no public exploit for CVE-2025-15469.
Is there a patch for CVE-2025-15469?
Upgrade OpenSSL 3.5 installations to 3.5.5 or later, or OpenSSL 3.6 installations to 3.6.1 or later. Distribution-maintained installations can instead apply vendor packages containing the backported fix, including RHEL 9 package version 3.5.1-7.el9_7, RHEL 10 package version 3.5.1-7.el10_1, or Echo package version 3.5.0+e1 or later.
What products are affected by CVE-2025-15469?
OpenSSL Software Foundation Openssl.
How severe is CVE-2025-15469?
CVE-2025-15469 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 0.21% (12th percentile) as of Nov 6, 2026.
Activity feed

Recent activity

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

View more in app →
+8 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 activity11Community discussion across Reddit, Mastodon, and other social sources.