Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2025-69420: OpenSSL TimeStamp Response Verification Type Confusion

Published Jan 27, 2026 · Updated 10 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 4 in a dayToday
CVSS7.5High · v3.1
EPSS0.92%61st percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
OpenSSL Software Foundation
IdentifiersCVE-2025-69420CWE-843

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.

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.

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.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
PoC-CVE-2025-69420This repository is a crash-only proof-of-concept for CVE-2025-69420 affecting OpenSSL TimeStamp Response verification. The core exploit logic is in poc.c, a standalone C program that loads a valid RFC 3161 TimeStamp Response, extracts the PKCS#7 signer info, locates the ESS SigningCertificateV2 or SigningCertificate signed attribute, verifies that its ASN.1 type is V_ASN1_SEQUENCE, then deliberately mutates that in-memory ASN.1 type to V_ASN1_NULL using ASN1_TYPE_set(). It then invokes TS_RESP_verify_response() with a trust store containing the TSA certificate. On affected OpenSSL builds, the verification path dereferences the ASN1_TYPE union as though it still contained a sequence, producing a UBSan null member access and process termination. This demonstrates denial-of-service/type-confusion behavior only; there is no remote delivery mechanism, no shell payload, and no code execution logic. Repository structure is minimal and purpose-built. poc.c is the main entry point and only exploit implementation. scripts/prepare.sh generates all local fixtures needed for reproduction: a temporary TSA key/certificate, a data file, a timestamp query, a TSA serial file, and a valid timestamp response using the local OpenSSL CLI. scripts/build.sh compiles the PoC against a user-supplied ASan/UBSan OpenSSL build with libcrypto. scripts/run.sh sets sanitizer environment variables and executes the PoC with response.tsr and tsa.crt. scripts/common.sh centralizes environment setup and validates the local OpenSSL binary and libcrypto path. openssl.cnf and tsa.conf are minimal OpenSSL/TSA configuration files used to create the test artifacts. evidence/confirmed-output.txt contains a shortened sanitizer trace confirming the crash path. The exploit is best classified as a local/file-based PoC rather than a weaponized exploit. It requires a locally controlled vulnerable OpenSSL build and crafted timestamp response artifacts. Fingerprintable artifacts are almost entirely local file paths and configuration references; there are no hardcoded remote IPs, domains, C2 endpoints, or network callbacks in the code.Kha-Beleh · Disclosed Jul 22, 2026 · c · bash · local · filePoC
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-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.
Activity feed

Recent activity

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

View more in app →
tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.0 : openssl (EulerOS-SA-2026-4609) | Tenable®OpenSSL timestamp-response verification can dereference an invalid or NULL pointer when processing malformed signing-certificate attributes, causing denial of service. Exploitation requires an application to verify an attacker-supplied TimeStamp Response. The advisory assesses the issue as low severity.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.1 : edk2 (EulerOS-SA-2026-4683) | Tenable®OpenSSL TimeStamp Response verification accesses signing-certificate ASN.1 attributes without validating their type. A malicious response can trigger type confusion and an invalid or NULL pointer dereference, crashing the verifying application. The advisory assesses the issue as Low severity; OpenSSL 1.0.2 is unaffected.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.1 : openssl (EulerOS-SA-2026-4567) | Tenable®OpenSSL TimeStamp Response verification contains an ASN1_TYPE type confusion in signing-certificate attribute handling. Processing an attacker-supplied malformed response can crash the application. The advisory rates this issue Low severity. OpenSSL 1.0.2 and the listed FIPS modules are unaffected.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.0 : edk2 (EulerOS-SA-2026-4741) | Tenable®OpenSSL timestamp-response verification accesses a signing-certificate ASN1_TYPE union member without validating its type. A crafted response can trigger an invalid or NULL pointer read in ossl_ess_get_signing_cert() or ossl_ess_get_signing_cert_v2(), crashing the verifying application. The advisory assesses severity as Low. OpenSSL 1.0.2 and the listed FIPS modules are unaffected. Exploit availability is reported only at the aggregate plugin level, not specifically for this CVE.Read more ↗
+21 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 activity19Community discussion across Reddit, Mastodon, and other social sources.