ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-69420

Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, caus

Published Jan 27, 2026 · catalog updated Oct 15, 2026 · Issue summary: A type

Last checked Nov 5, 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-69420. EPSS is 0.92%. Act only if a listed version of Issue summary: A type 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: A type).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.92%
Remediation
Version ranges on file
Affected products
cpe openssl/openssl · vendor OpenSSL OpenSSL 3.0.0 <3.0.19

Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file. Impact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service. The functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type. When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash. Exploiting this vulnerability requires an attacker to provide a malformed TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161) is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue was assessed as Low severity. The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue. OpenSSL 1.0.2 is 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< 1.1.1ze
  • cpe openssl/openssl< 3.0.19
  • cpe openssl/openssl< 3.3.6
  • cpe openssl/openssl< 3.4.4
  • cpe openssl/openssl< 3.5.5
  • cpe openssl/openssl< 3.6.1
  • vendor OpenSSL OpenSSL 3.0.0 <3.0.193.0.0 <3.0.19

How to fix CVE-2025-69420

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-69420. EPSS is 0.92%. Act only if a listed version of Issue summary: A type is installed.

Which versions are affected?

Compare what you have installed with OpenSSL OpenSSL 3.0.0 <3.0.19 3.0.0 <3.0.19. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-754. EPSS 0.92%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

OpenSSL security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jan 27, 2026 · EUVD

    Detected

    Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file. Impact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to derefe

  2. Oct 15, 2026 · EUVD

    Updated

    Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file. Impact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to derefe

Sources

  • CVE.orgVulnerability recordCVE-2025-69420

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-69420

    30-day exploitation probability 0.92%

    first.org
  • EUVDVulnerability recordEUVD-2025-206394

    Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file. Impa

    euvd.enisa.europa.eu
  • Monitored products — criticalVendor advisoryCVE-2025-69420

    Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file. Impact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to derefe

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 5, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSNov 5, 2026
  • Monitored products — criticalNov 4, 2026
  • CVE.orgNov 4, 2026
  • EUVDNov 2, 2026