CVE-2022-3786

CRITICALNVD 7.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 92% probability of exploitation within the next 30 days (top 0.2% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 92%
CISA-KEV: Not listedEPSS PROB: 92%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed a malicious certificate or for an application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a certificate to overflow an arbitrary number of bytes containing the `.' character (decimal 46) on the stack. This buffer overflow could result in a crash (causing a denial of service). In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.

CVSS v3
7.5
EG Score
9.0(high)
EG Risk
92(Track)
EG Risk 92/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
Severity90% × 45%
Exploitation92% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
92%
EPSS %ILE
100%
KEV
Not listed

Published

November 1, 2022

Last Modified

April 14, 2026

References (7)

Vendor Advisories for CVE-2022-3786(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibssl3 (3.0.5-2ubuntu2) @ kinetic2026-05-22ubuntu
redhatubi9/openssl:9.0-252022-11-02redhat
redhatopenssl-1:3.0.1-43.el9_02022-11-01redhat

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

(22 across 14 ecosystems)
Alpine:v3.17(2)
PackageVulnerable rangeFixed inDependents
nodejs—18.12.1-r0—
openssl—3.0.7-r0—
Alpine:v3.18(2)
PackageVulnerable rangeFixed inDependents
nodejs—18.12.1-r0—
openssl—3.0.7-r0—
Alpine:v3.19(2)
PackageVulnerable rangeFixed inDependents
nodejs—18.12.1-r0—
openssl—3.0.7-r0—
Alpine:v3.20(2)
PackageVulnerable rangeFixed inDependents
nodejs—18.12.1-r0—
openssl—3.0.7-r0—
Alpine:v3.21(2)
PackageVulnerable rangeFixed inDependents
nodejs—18.12.1-r0—
openssl—3.0.7-r0—
Alpine:v3.22(2)
PackageVulnerable rangeFixed inDependents
nodejs—18.12.1-r0—
openssl—3.0.7-r0—
Alpine:v3.23(2)
PackageVulnerable rangeFixed inDependents
nodejs—18.12.1-r0—
openssl—3.0.7-r0—
Alpine:v3.24(2)
PackageVulnerable rangeFixed inDependents
nodejs—18.12.1-r0—
openssl—3.0.7-r0—
Alpine:v3.15(1)
PackageVulnerable rangeFixed inDependents
openssl3—3.0.7-r0—
Alpine:v3.16(1)
PackageVulnerable rangeFixed inDependents
openssl3—3.0.7-r0—
crates.io(1)
PackageVulnerable rangeFixed inDependents
openssl-src—300.0.11—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssl—3.0.7-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl—3.0.7-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl—3.0.7-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 3× in last 7d / 11× 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 107 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCWhatTheFuzz/openssl-fuzz
    First seen Jan 11, 2023

    Finding CVE-2022-3786 (openssl) with Mayhem

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-3786?
CVE-2022-3786 is a critical vulnerability published on November 1, 2022. A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed a malicious certificate or for an application to continue certificate…
When was CVE-2022-3786 disclosed?
CVE-2022-3786 was first published in the National Vulnerability Database on November 1, 2022, with the most recent update on April 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-3786 actively exploited?
CVE-2022-3786 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 92% probability of exploitation in the next 30 days, which ranks it in the top 0.2% of all scored CVEs.
What is the CVSS score of CVE-2022-3786?
CVE-2022-3786 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2022-3786?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-3786, 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-2022-3786

Explore →

Is Your Infrastructure Affected by CVE-2022-3786?

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

Start Free Scan →Browse All CVEs