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.
CVE-2022-3786
“▲” beside the score: it is higher than NVD's CVSS score.
Score elevated to 9.0 because EPSS predicted 92% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.
- High exploitation likelihood — EPSS 92%
- Public exploit or proof-of-concept code is available
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 9.0CRITICALhigh confidence
- EG Risk
- 86EG Risk 86/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation92% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 92%
- EPSS %ILE
- 99th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.5 HIGH): a likelihood of exploitation, not impact.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 92% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 1, 2022
Last Modified
April 14, 2026
Advisory Details (4)
Auto-updated Oct 15, 2026VU#794340 - OpenSSL 3.0.0 to 3.0.6 decodes some punycode email addresses in X.509 certificates improperly
https://www.kb.cert.org/vuls/id/794340INTEL-SA-00789
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00789.htmlVendor Advisories for CVE-2022-3786(4)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2022:7384Red Hat Product SecurityHigh
Red Hat Security Advisory: openssl-container security update
- CVE-2022-3786Microsoft Security Response Center (MSRC)
OpenSSL: CVE-2022-3786 X.509 certificate verification buffer overrun
- RHSA-2022:7288Red Hat Product SecurityHigh
Red Hat Security Advisory: openssl security update
- PAN-SA-2022-0006Palo Alto Networks Security AdvisoriesNone
PAN-SA-2022-0006 Impact of OpenSSL 3.0 Vulnerabilities CVE-2022-3786 and CVE-2022-3602
Patch Availability(3)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libssl3 (3.0.2-0ubuntu1.7) @ jammy | 2026-10-22 | ubuntu |
| redhat | ubi9/openssl:9.0-25 | 2022-11-02 | redhat |
| redhat | openssl-1:3.0.1-43.el9_0 | 2022-11-01 | redhat |
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)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
| openssl | — |
| — |
Alpine:v3.18(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
| openssl | — |
| — |
Alpine:v3.19(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
| openssl | — |
| — |
Alpine:v3.20(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
| openssl | — |
| — |
Alpine:v3.21(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
| openssl | — |
| — |
Alpine:v3.22(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
| openssl | — |
| — |
Alpine:v3.23(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
| openssl | — |
| — |
Alpine:v3.24(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
| openssl | — |
| — |
Alpine:v3.15(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl3 | — |
| — |
Alpine:v3.16(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl3 | — |
| — |
crates.io(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl-src | — |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
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 17× in last 7d / 34× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 78 of 122 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 22 repeat rows among the latest 100 are merged into the row they repeat. The 44 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-23 15:26 UTCEG score recompute
- 2026-10-23 15:26 UTCVendor advisory
- 2026-10-22 13:43 UTCEG score recompute
- 2026-10-22 13:43 UTCVendor advisory
- 2026-10-21 16:29 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-10-21 12:05 UTCEG score recompute
- 2026-10-21 12:05 UTCVendor advisory
- 2026-10-20 10:24 UTCEG score recompute
- 2026-10-20 10:24 UTCVendor advisory
- 2026-10-19 16:28 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-10-19 08:44 UTCEG score recompute
- 2026-10-19 08:44 UTCVendor advisory
- 2026-10-18 07:05 UTCEG score recompute
- 2026-10-18 07:05 UTCVendor advisory
- 2026-10-17 16:29 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-10-17 05:21 UTCEG score recompute
- 2026-10-17 05:21 UTCVendor advisory
- 2026-10-16 03:40 UTCEG score recompute
- 2026-10-16 03:40 UTCVendor advisory
- 2026-10-15 16:28 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-10-15 00:31 UTCEG score recompute
- 2026-10-15 00:31 UTCVendor advisory
- 2026-10-14 16:29 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-10-13 20:21 UTCEG score recompute
- 2026-10-13 20:21 UTCVendor advisory
Show 53 moreShow fewer
- 2026-10-12 18:14 UTCEG score recompute
- 2026-10-12 18:14 UTCVendor advisory
- 2026-10-11 23:13 UTCEG score recompute
- 2026-10-07 23:45 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-09-30 20:40 UTCOSV refresh
- 2026-09-30 16:01 UTCEG score recompute
- 2026-09-30 15:01 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-09-27 13:42 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-09-26 15:55 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-09-23 13:45 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-09-15 03:07 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-09-12 02:53 UTCOSV refresh
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-09-05 15:25 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-09-02 14:09 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-08-30 19:14 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-08-28 21:38 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-08-24 14:13 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-08-24 08:27 UTCOSV refresh
- 2026-08-19 17:01 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-08-12 13:48 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-08-08 04:49 UTCOSV refresh
- 2026-08-05 19:15 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-07-30 01:28 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-07-24 14:15 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-07-23 02:13 UTCEG score recompute
- 2026-07-22 21:26 UTCEG score recompute▲ 1.50
- 2026-07-22 21:26 UTCVendor advisory
- 2026-07-22 14:06 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-07-15 16:56 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-07-11 12:52 UTCOSV refresh
- 2026-07-06 16:25 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-06-28 04:54 UTCEPSS rescoreEPSS 91% · 99th percentile
- 2026-06-23 21:31 UTCEPSS rescoreEPSS 91% · 99th percentile
- 2026-06-22 19:35 UTCOSV refresh
- 2026-06-16 17:51 UTCEPSS rescoreEPSS 91% · 99th percentile
- 2026-06-15 17:46 UTCEPSS rescoreEPSS 91% · 99th percentile
- 2026-06-14 23:15 UTCEPSS rescoreEPSS 27% · 96th percentile
- 2026-06-13 22:58 UTCEPSS rescoreEPSS 27% · 96th percentile
- 2026-06-12 23:10 UTCEPSS rescoreEPSS 27% · 96th percentile
- 2026-06-11 13:58 UTCEPSS rescoreEPSS 27% · 96th percentile
- 2026-06-10 22:17 UTCEPSS rescoreEPSS 27% · 96th percentile
- 2026-06-10 13:20 UTCEPSS rescoreEPSS 27% · 96th percentile
- 2026-06-06 13:46 UTCEPSS rescoreEPSS 27% · 96th percentile
- 2026-06-05 22:45 UTCEPSS rescoreEPSS 27% · 96th percentile
- 2026-06-05 09:30 UTCOSV refresh
- 2026-06-05 06:09 UTCEPSS rescoreEPSS 27% · 96th percentile
- 2026-06-04 13:11 UTCEPSS rescoreEPSS 27% · 96th percentile
- 2026-06-02 20:11 UTCEPSS rescoreEPSS 27% · 96th percentile
- 2026-06-01 13:50 UTCEPSS rescoreEPSS 27% · 96th percentile
- 2026-05-31 22:29 UTCEPSS rescoreEPSS 27% · 96th percentile
- 2026-05-31 00:15 UTCEPSS rescoreEPSS 27% · 96th percentile
- 2026-05-29 13:43 UTCEPSS rescoreEPSS 27% · 96th percentile
Publicly available exploits
(1 reference)Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.
- GitHub PoCWhatTheFuzz/openssl-fuzzPublished Jan 11, 2023
Finding CVE-2022-3786 (openssl) with Mayhem
Open source ↗
Related CVEs(same product + same vendor + same CWE)
Same product
10 showncrates.io:openssl-src · Alpine:v3.15:openssl3
- CVE-2022-3602NVD 7.5EG 9.0EPSS p100CRITICAL
- CVE-2018-0734EG 5.9EPSS p96MEDIUM
- CVE-2018-0735EG 5.9EPSS p92MEDIUM
- CVE-2021-3711EG 9.8EPSS p100CRITICAL
- CVE-2022-0778NVD 7.5EG 8.7EPSS p99HIGH
- CVE-2023-0286NVD 7.4EG 8.6EPSS p99HIGH
- CVE-2021-23840NVD 7.5EG 8.1EPSS p99HIGH
- CVE-2020-1967NVD 7.5EG 8.1EPSS p99HIGH
- CVE-2021-3712NVD 7.4EG 8.0EPSS p99HIGH
- CVE-2021-3449NVD 5.9EG 7.8EPSS p99HIGH
Same vendor
2 shownredhat:RHSA-2022:7288 · ubuntu:USN-5710-1
Frequently asked(5)
What is CVE-2022-3786?
When was CVE-2022-3786 made public?
Is CVE-2022-3786 actively exploited?
What is the CVSS score of CVE-2022-3786?
How do I remediate CVE-2022-3786?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-3786
Is Your Infrastructure Affected by CVE-2022-3786?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.