CVE-2026-42765

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-09. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Issue summary: When a partial-chain certificate verification is enabled together with OCSP response checking for the whole chain, a NULL dereference will happen if the verified chain does not have a self-signed trusted anchor, crashing the process.

Impact summary: A NULL pointer dereference can trigger a crash which leads to a Denial of Service for an application.

When performing OCSP response checking for certificates in the verification chain, the code always tries to access the next certificate as the issuer. There is a check for a self-signed certificate. However with the partial chain verification enabled when the chain does not have a self-signed trusted anchor, the issuer will be NULL for the last certificate in the chain. A NULL pointer dereference then happens.

This issue affects only applications which enable both OCSP verification of the certificate chain (X509_V_FLAG_OCSP_RESP_CHECK_ALL) and partial chain verification (X509_V_FLAG_PARTIAL_CHAIN) in the certificate verification. Both flags are disabled by default. For that reason, we have assigned Low severity to the issue.

No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jun 10, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic
https://openssl-library.org/news/secadv/20260609.txt
github_commit

commit eb345da18ce2 (openssl/openssl)

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

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

commit 14340b7fa1d4 (openssl/openssl)

Fix landed in openssl/openssl commit 14340b7fa1d4 — awaiting tagged release

https://github.com/openssl/openssl/commit/14340b7fa1d444615486bc137014b064e64ec334

Vendor Advisories for CVE-2026-42765(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 3.6.2-1 (21 versions)3.6.3-1—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 41× 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 240 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-42765?
CVE-2026-42765 is a high vulnerability published on June 9, 2026. Issue summary: When a partial-chain certificate verification is enabled together with OCSP response checking for the whole chain, a NULL dereference will happen if the verified chain does not have a self-signed trusted anchor, crashing the process. Impact summary: A NULL pointer dereference can…
When was CVE-2026-42765 disclosed?
CVE-2026-42765 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42765 actively exploited?
CVE-2026-42765 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 58.1% of all scored CVEs.
What is the CVSS score of CVE-2026-42765?
CVE-2026-42765 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-42765?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42765, 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-2026-42765

Explore →

Is Your Infrastructure Affected by CVE-2026-42765?

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

Start Free Scan →Browse All CVEs