CVE-2025-69420

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-01-27. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
54%
KEV
Not listed

Published

January 27, 2026

Last Modified

June 17, 2026

Advisory Details (7)

Auto-updated Aug 6, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

SSA-265688

https://cert-portal.siemens.com/productcert/html/ssa-265688.html
generic
https://openssl-library.org/news/secadv/20260127.txt
github_commit

commit a99349ebfc51 (openssl/openssl)

Fix landed in openssl/openssl commit a99349ebfc51 — awaiting tagged release

https://github.com/openssl/openssl/commit/a99349ebfc519999edc50620abe24d599b9eb085
github_commit

commit 5eb0770ffcf1 (openssl/openssl)

Fix landed in openssl/openssl commit 5eb0770ffcf1 — awaiting tagged release

https://github.com/openssl/openssl/commit/5eb0770ffcf11b785cf374ff3c19196245e54f1b
github_commit

commit 564fd9c73787 (openssl/openssl)

Fix landed in openssl/openssl commit 564fd9c73787 — awaiting tagged release

https://github.com/openssl/openssl/commit/564fd9c73787f25693bf9e75faf7bf6bb1305d4e
github_commit

commit 4e254b48ad93 (openssl/openssl)

Fix landed in openssl/openssl commit 4e254b48ad93 — awaiting tagged release

https://github.com/openssl/openssl/commit/4e254b48ad93cc092be3dd62d97015f33f73133a
github_commit

commit 27c7012c91cc (openssl/openssl)

Fix landed in openssl/openssl commit 27c7012c91cc — awaiting tagged release

https://github.com/openssl/openssl/commit/27c7012c91cc986a598d7540f3079dfde2416eb9

Vendor Advisories for CVE-2025-69420(8)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl-provider-legacy (3.5.3-1ubuntu3) @ questing2026-06-08ubuntu
ubuntuopenssl (1.0.1f-1ubuntu2.27+esm12) @ trusty2026-06-08ubuntu
redhatopenssl-main-3.5.6-0.1.hum12026-04-09redhat
redhatrhui5/rhua-rhel9:17736701372026-03-18redhat
redhatcostmanagement/costmanagement-metrics-rhel9-operator:17708363492026-02-24redhat
redhatrhui5/installer-rhel9:17706469252026-02-11redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17707404052026-02-10redhat
redhatdiscovery/discovery-ui-rhel9:17691117742026-02-02redhat
redhatopenssl-1:3.5.1-7.el10_12026-01-28redhat
redhatopenssl-1:3.5.1-7.el9_72026-01-28redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(10 across 10 ecosystems)
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
openssl—3.0.19-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
openssl—3.3.6-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
openssl—3.3.6-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
openssl—3.5.5-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
openssl—3.5.5-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
openssl—3.5.5-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
openssl1.1.1k-1 ... 1.1.1w-0~deb11u1 (20 versions)1.1.1w-0+deb11u5—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssl3.0.10-1 ... 3.0.9-1 (18 versions)3.0.18-1~deb12u2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1, 3.5.1-1+deb13u1, 3.5.2-1, 3.5.3-1, 3.5.4-1~deb13u13.5.4-1~deb13u2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 3.5.5-1~deb13u2 (8 versions)3.5.5-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 49× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 180 total refreshes for this CVE.

  1. 2026-08-30 01:21 UTCEPSS rescore
  2. 2026-08-28 21:40 UTCEPSS rescore
  3. 2026-08-27 14:24 UTCEPSS rescore
  4. 2026-08-26 14:45 UTCEPSS rescore
  5. 2026-08-25 13:48 UTCEPSS rescore
  6. 2026-08-24 14:16 UTCEPSS rescore
  7. 2026-08-23 00:18 UTCEPSS rescore
  8. 2026-08-21 23:48 UTCEPSS rescore
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-19 17:03 UTCEPSS rescore
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 13:46 UTCEPSS rescore
  13. 2026-08-16 14:55 UTCEPSS rescore
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-15 00:59 UTCVendor advisory
  17. 2026-08-15 00:59 UTCGHSA enrichment
  18. 2026-08-14 12:11 UTCEG score recompute
  19. 2026-08-14 12:11 UTCVendor advisory
  20. 2026-08-14 12:11 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 04:16 UTCEG score recompute
  23. 2026-08-13 04:16 UTCVendor advisory
  24. 2026-08-13 04:16 UTCGHSA enrichment
  25. 2026-08-12 13:50 UTCEPSS rescore
Show 75 more
  1. 2026-08-11 13:42 UTCEPSS rescore
  2. 2026-08-10 23:59 UTCEPSS rescore
  3. 2026-08-10 10:25 UTCVendor advisory
  4. 2026-08-10 10:25 UTCGHSA enrichment
  5. 2026-08-09 17:58 UTCEG score recompute
  6. 2026-08-09 17:58 UTCVendor advisory
  7. 2026-08-09 17:58 UTCGHSA enrichment
  8. 2026-08-09 13:46 UTCEPSS rescore
  9. 2026-08-08 16:36 UTCEPSS rescore
  10. 2026-08-07 23:24 UTCEG score recompute
  11. 2026-08-07 23:24 UTCVendor advisory
  12. 2026-08-07 23:24 UTCGHSA enrichment
  13. 2026-08-07 16:27 UTCEPSS rescore
  14. 2026-08-06 13:46 UTCEPSS rescore
  15. 2026-08-06 04:53 UTCEG score recompute
  16. 2026-08-06 04:53 UTCVendor advisory
  17. 2026-08-06 04:53 UTCGHSA enrichment
  18. 2026-08-05 19:17 UTCEPSS rescore
  19. 2026-08-04 10:37 UTCEPSS rescore
  20. 2026-08-03 10:35 UTCEPSS rescore
  21. 2026-08-02 22:02 UTCEG score recompute
  22. 2026-08-02 22:02 UTCVendor advisory
  23. 2026-08-02 22:02 UTCGHSA enrichment
  24. 2026-08-02 02:26 UTCEPSS rescore
  25. 2026-08-01 04:15 UTCEPSS rescore
  26. 2026-07-31 06:42 UTCOSV refresh
  27. 2026-07-30 16:27 UTCEPSS rescore
  28. 2026-07-30 01:30 UTCEPSS rescore
  29. 2026-07-27 14:13 UTCEPSS rescore
  30. 2026-07-26 14:54 UTCEPSS rescore
  31. 2026-07-26 14:54 UTCEPSS rescore
  32. 2026-07-25 14:17 UTCEPSS rescore
  33. 2026-07-25 14:17 UTCEPSS rescore
  34. 2026-07-24 14:17 UTCEPSS rescore
  35. 2026-07-23 14:18 UTCEPSS rescore
  36. 2026-07-23 14:18 UTCEPSS rescore
  37. 2026-07-23 03:02 UTCEG score recompute
  38. 2026-07-22 14:08 UTCEPSS rescore
  39. 2026-07-21 15:24 UTCEPSS rescore
  40. 2026-07-20 17:08 UTCEPSS rescore
  41. 2026-07-19 14:30 UTCEPSS rescore
  42. 2026-07-19 14:30 UTCEPSS rescore
  43. 2026-07-19 02:28 UTCEPSS rescore
  44. 2026-07-19 02:28 UTCEPSS rescore
  45. 2026-07-18 10:04 UTCEPSS rescore
  46. 2026-07-18 10:04 UTCEPSS rescore
  47. 2026-07-16 17:02 UTCEPSS rescore
  48. 2026-07-16 17:02 UTCEPSS rescore
  49. 2026-07-15 16:57 UTCEPSS rescore
  50. 2026-07-15 16:57 UTCEPSS rescore
  51. 2026-07-15 02:00 UTCEPSS rescore
  52. 2026-07-15 01:59 UTCEPSS rescore
  53. 2026-07-13 14:08 UTCOSV refresh
  54. 2026-07-13 06:12 UTCEPSS rescore
  55. 2026-07-12 05:46 UTCEPSS rescore
  56. 2026-07-12 05:46 UTCEPSS rescore
  57. 2026-07-11 08:27 UTCEPSS rescore
  58. 2026-07-11 08:27 UTCEPSS rescore
  59. 2026-07-09 19:10 UTCEPSS rescore
  60. 2026-07-08 15:15 UTCEPSS rescore
  61. 2026-07-07 13:46 UTCEPSS rescore
  62. 2026-07-06 16:27 UTCEPSS rescore
  63. 2026-07-06 02:23 UTCEPSS rescore
  64. 2026-07-05 02:30 UTCEPSS rescore
  65. 2026-07-05 02:30 UTCEPSS rescore
  66. 2026-07-04 06:31 UTCEPSS rescore
  67. 2026-07-04 06:31 UTCEPSS rescore
  68. 2026-07-01 15:06 UTCEPSS rescore
  69. 2026-06-30 23:22 UTCEPSS rescore
  70. 2026-06-30 23:22 UTCEPSS rescore
  71. 2026-06-29 14:06 UTCEPSS rescore
  72. 2026-06-29 14:06 UTCEPSS rescore
  73. 2026-06-28 14:07 UTCEPSS rescore
  74. 2026-06-28 14:07 UTCEPSS rescore
  75. 2026-06-28 04:56 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-69420?
CVE-2025-69420 is a high vulnerability published on January 27, 2026. 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…
When was CVE-2025-69420 disclosed?
CVE-2025-69420 was first published in the National Vulnerability Database on January 27, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-69420 actively exploited?
CVE-2025-69420 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 46.0% of all scored CVEs.
What is the CVSS score of CVE-2025-69420?
CVE-2025-69420 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2025-69420?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-69420, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-69420

Explore →

Is Your Infrastructure Affected by CVE-2025-69420?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs