Finding and attribution
A malformed TimeStamp Response can cause invalid or NULL-pointer access in `TS_RESP_verify_response()` because the signing-certificate attribute type is not validated. OpenSSL says the RFC 3161 protocol is not widely used and impact is denial of service.
Product: OpenSSL. AI system: AISLE autonomous analyzer (specific model/version not disclosed). Team / organization: AISLE.
CVE identifiers: CVE-2025-69420.
AI and human contribution (source account): AISLE’s January 26, 2026 article says its autonomous analyzer found all 12 CVEs in OpenSSL’s January coordinated release, and individually names this case. OpenSSL’s own vulnerability record credits the named Aisle Research finder(s) for CVE-2025-69420; OpenSSL’s January 27 security advisory gives the flaw and report chronology. The exact model and division of AI versus researcher analysis are not public. OpenSSL credits Luigino Camastra (Aisle Research) as finder; AISLE says its autonomous analyzer found all 12 cases. Exact human/AI division is not published.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: OpenSSL published the vendor advisory and released fixes on January 27, 2026. The AISLE public AI attribution article appeared January 26, one day before the public vendor disclosure. No claim of in-the-wild exploitation is made.
Remediation status: fix documented. OpenSSL 3.6.1, 3.5.5, 3.4.4, 3.3.6, 3.0.19 and 1.1.1ze (premium-support branch). See the OpenSSL advisory for affected release details; FIPS impact and exceptional configurations are stated in the advisory where applicable. This record does not establish deployment.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 27 Jan 2026. AI attribution dated 26 Jan 2026. Sources checked 15 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: High · highest recorded score 7.5. Documented technical effects: denial of service.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2025-69420: CVSS 3.1 · 7.5 (High) ·
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. CISA-ADP (ADP; CVE Program record) · checked 16 Nov 2026.
CVE-2025-69420: denial of service.
Prerequisites / affected scope: The CNA description states: 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..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
Documented fix: OpenSSL 3.6.1, 3.5.5, 3.4.4, 3.3.6, 3.0.19 and 1.1.1ze (premium-support branch). See the OpenSSL advisory for affected release details; FIPS impact and exceptional configurations are stated in the advisory where applicable. This record does not establish deployment.