VulnTideExploited vulnerabilities, by vendor. Data as of .
Not in CISA KEVPublished CVSS 7.5 highEPSS 0.9% probability of exploitation in 30 daysFound by AI: AISLE
OpenSSL

CVE-2025-69420: Missing ASN1_TYPE validation in TS_RESP_verify_response() function

Is it exploited?

Not on CISA's list. CISA has not added it to the Known Exploited Vulnerabilities catalog as of . If CISA adds it, this page shows it as known exploited.

How likely is exploitation in the next 30 days?
0.9%

EPSS score, percentile 60.2 of all scored records. A probability estimated by FIRST, not a report of exploitation.

How severe?
7.5 High

CVSS v3.1 base score, from CISA's enrichment of the record

What should I do?

CISA has set no required action, because the vulnerability is not in KEV.

Advisories and patches (6)

Which versions are affected?

Affected

  • from 3.6.0 to before 3.6.1
  • from 3.5.0 to before 3.5.5
  • from 3.4.0 to before 3.4.4
  • from 3.3.0 to before 3.3.6
  • from 3.0.0 to before 3.0.19
  • from 1.1.1 to before 1.1.1ze

Versions by product

Source: CISA KEV 2026.10.29, as of ; FIRST EPSS, as of ; CVE List, as of . About the data.

What to do

Advisories and patches

This summary is based on the CVE record as of . Check the vendor's advisory before you act: affected versions and fixes can change.

Affected products and versions

As listed in the CVE record.

OpenSSL OpenSSL
StatusVersions
Affectedfrom 3.6.0 to before 3.6.1
Affectedfrom 3.5.0 to before 3.5.5
Affectedfrom 3.4.0 to before 3.4.4
Affectedfrom 3.3.0 to before 3.3.6
Affectedfrom 3.0.0 to before 3.0.19
Affectedfrom 1.1.1 to before 1.1.1ze

Versions not listed are: unaffected.

Source: CVE List, as of . About the data.

About this vulnerability

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 dere…

Summary: CVE record, as of .

  • CISA has not added CVE-2025-69420 to its Known Exploited Vulnerabilities (KEV) catalog, as of 29 Oct 2026.
  • The CVE record was published on 27 Jan 2026.
  • The CVE record carries a CVSS v3.1 base score of 7.5 (High), taken from CISA's enrichment of the record.
  • FIRST's EPSS model puts the probability of exploitation in the next 30 days at 0.9% (percentile 60.2), as of 29 Oct 2026. EPSS is a statistical estimate, not a report of exploitation.
  • CISA's SSVC assessment in the CVE record: exploitation none, automatable yes, technical impact partial.
  • The credits in the CVE record name AISLE as finder.

Source: CISA KEV 2026.10.29, as of ; CVE List, as of ; FIRST EPSS, as of . About the data.

Description

Missing ASN1_TYPE validation in TS_RESP_verify_response() function

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.

Source: CVE List, as of . About the data.

Weakness

CWE-754
  • CWE-754: Improper Check for Unusual or Exceptional Conditions

CWE and CAPEC are maintained by MITRE; the entries are those named in the CVE record.

Timeline

DateEvent
CVE record published
CVE record last updated

Known exploited OpenSSL vulnerabilities

  • CVE-2014-0160: OpenSSL Information Disclosure Vulnerability (added )