CVE-2025-69420: OpenSSL TimeStamp Response Verification Type Confusion
- Vendor
- OpenSSL Software Foundation
CVE-2025-69420 is a type confusion vulnerability in OpenSSL's RFC 3161 TimeStamp Response verification implementation. The functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2() access signing-certificate attribute values through an ASN1_TYPE union without confirming that the attribute type is V_ASN1_SEQUENCE. A malformed response containing an unexpected attribute type can therefore trigger an invalid or NULL pointer read when an application calls TS_RESP_verify_response(), crashing the application. Affected release branches include OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, and 1.1.1; OpenSSL 1.0.2 is unaffected. The OpenSSL FIPS modules in branches 3.5, 3.4, 3.3, and 3.0 are unaffected because timestamp-response verification is outside their module boundaries.
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.
Successful exploitation causes denial of service by crashing the application performing timestamp-response verification. The established impact is limited to availability; code execution, information disclosure, and integrity compromise are not established. OpenSSL assessed the issue as Low severity because RFC 3161 timestamp verification is relatively uncommon and the impact is limited to denial of service. Applications using an affected OpenSSL library can remain vulnerable even when using an unaffected FIPS module.
Mitigation
If you can’t patch tonight, do this now.
Until patched, avoid processing untrusted RFC 3161 TimeStamp Responses or restrict accepted responses to trusted sources. Isolate timestamp verification in a separate process or sandbox to limit the effect of a verifier crash on the main application. These measures reduce exposure or contain availability impact but do not correct the underlying type confusion.
Remediation
Patch, then assume compromise.
Install an OpenSSL or operating-system vendor update explicitly addressing CVE-2025-69420. Identified fixed releases for the affected OpenSSL 3.x branches are 3.6.1, 3.5.5, 3.4.4, 3.3.6, and 3.0.19, respectively. Vendor-backported packages may retain earlier upstream version numbers; identified RHEL updates include 3.5.1-7.el9_7 and 3.5.1-7.el10_1. For OpenSSL 1.1.1 or products embedding OpenSSL, obtain the applicable vendor-supported security update. Restart dependent applications after replacing shared libraries, and rebuild applications that statically link the vulnerable implementation.
Exploits
1 exploit validated by Mallory's analysis.
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.
References
Frequently asked questions
- Is CVE-2025-69420 exploited in the wild?
- As of Nov 7, 2026, Mallory has no reports of CVE-2025-69420 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2025-69420?
- Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2025-69420, the earliest disclosed Jul 22, 2026.
- Is there a patch for CVE-2025-69420?
- Install an OpenSSL or operating-system vendor update explicitly addressing CVE-2025-69420. Identified fixed releases for the affected OpenSSL 3.x branches are 3.6.1, 3.5.5, 3.4.4, 3.3.6, and 3.0.19, respectively.
- What products are affected by CVE-2025-69420?
- OpenSSL Software Foundation Openssl.
- How severe is CVE-2025-69420?
- CVE-2025-69420 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.92% (61st percentile) as of Nov 7, 2026.
Recent activity
53 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.