CVE-2025-69420Disclosure(openssl / openssl)

LOWCVSS 7.5 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

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.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-754

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • openssl

Threat summary

  • 6 mentions across 6 observed days
  • Momentum state: stable

What's happening

  • Technical details provided in 1 signal
  • Disclosure: 2 classified signals
  • General: 2 classified signals
  • False Positive: 2 classified signals
  • Peaked 5d ago at 1 mentions (2026-01-27); latest day: 1
  • 6 total mentions across 6 days

Affected systems

Vendors
Products
openssl

Deep dive

Activity timeline6 mentions / 6d
00111Mentions · 2026-01-27: 1Mentions · 2026-02-04: 1Mentions · 2026-02-19: 1Mentions · 2026-03-14: 1Mentions · 2026-03-15: 1Mentions · 2026-09-01: 1Technical Details · 2026-02-19: 101-2702-0402-1903-1403-1509-01
Signal classification3 categories
Disclosure
233.3%
General
233.3%
False Positive
233.3%
Referenced assets5 URLs
Classification over time
DateTotalLabels
2026-01-271
Disclosure1
2026-02-041
General1
2026-02-191
Disclosure1
2026-03-141
False Positive1
2026-03-151
False Positive1
2026-09-011
General1
Full discourse6 posts
  • solst/ICE of Astarte@IceSolst
    General

    @ErikExplains https://www.cve.org/CVERecord?id=CVE-2025-69420 Imagine getting assigned this ID and putting it on your resume, just to have nobody take you seriously

    Post summary

    The tweet simply links to a CVE record, providing no technical or exploitation details about the vulnerability.

    2001711.4K
    33.0K followersView on X
  • Lambda Watchdog@LambdaWatchdog
    False Positive

    🔍 Lambda Watchdog detected that CVE-2025-69420 is no longer present in latest AWS Lambda base image scans. https://github.com/aws/aws-lambda-base-images/issues/420 #AWS #Lambda #Security #CVE #DevOps #SecOps

    Post summary

    The message reports that CVE‑2025‑69420 is no longer detected in the latest AWS Lambda base image scans, indicating the vulnerability is effectively moot or was a false positive.

    00000153
    32 followersView on X
  • Lambda Watchdog@LambdaWatchdog
    False Positive

    🔍 Lambda Watchdog detected that CVE-2025-69420 is no longer present in latest AWS Lambda base image scans. https://github.com/aws/aws-lambda-base-images/issues/420 #AWS #Lambda #Security #CVE #DevOps #SecOps

    Post summary

    AWS Lambda base images have been updated to no longer contain CVE‑2025‑69420, effectively negating the vulnerability for those images.

    00000164
    31 followersView on X
  • Lambda Watchdog@LambdaWatchdog
    Disclosure

    🚨 New HIGH CVE detected in AWS Lambda 🚨 CVE-2025-69420 impacts openssl-fips-provider-latest in 40 Lambda base images. Details: https://github.com/aws/aws-lambda-base-images/issues/420 More: https://lambdawatchdog.com/ #AWS #Lambda #CVE #CloudSecurity #Serverless

    Post summary

    The tweet announces a newly detected high‑severity CVE (CVE‑2025‑69420) affecting the openssl‑fips‑provider component in AWS Lambda base images, with links to issue details but no exploitation or patch information yet.

    0000044
    30 followersView on X
  • Stuart 🇨🇷@stooee_
    General

    After analyzing 52% of vulnerabilities from past week, CVE-2025-69420 has 47 articles published from different internet sources, no other cve has these many articles. More information here: https://cves.st00ee.com/ #vulnerability #CyberSecurity #ThreatIntel #CVE #SecurityAlert

    Post summary

    The post notes that CVE-2025-69420 has a high volume of articles but offers no technical details, PoC, or evidence of exploitation.

    0000058
    73 followersView on X
  • 〒@teenigma_
    Disclosure

    oss-sec: OpenSSL Security Advisory Moderate: CVE-2025-11187 High: CVE-2025-15467 Low: CVE-2025-15468, CVE-2025-15469, CVE-2025-66199, CVE-2025-68160, CVE-2025-69418, CVE-2025-69419, CVE-2025-69420, CVE-2025-69421, CVE-2026-22795, CVE-2026-22796 https://seclists.org/oss-sec/2026/q1/123

    Post summary

    This post is a concise OpenSSL security advisory listing multiple CVEs with severity ratings and a link to the full advisory, without any PoC, exploit, or patch details.

    00000156
    348 followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appopensslopenssl---

Explore more