CVE-2026-35190

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.3 from GitHub Security Advisory (severity: MODERATE) published 2026-11-17. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory

Also known asEUVD-2026-126929 (ENISA EUVD) · GHSA-r3mj-hq6x-h82q (GitHub Security Advisories)Source: ENISA EUVD

5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group.

Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service.

CWE: CWE-125: Out-of-bounds Read

Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present.

Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code.

A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data.

FIPS impact: no The affected code is outside the FIPS module boundary.

CVSS v3
5.3
EG Score
5.3MEDIUMhigh confidence
EG Risk
39
EG Risk 39/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)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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
0.2%
EPSS %ILE
14th
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 (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. 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, and whom BOD 26-04 binds: 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.

The score's inputs: 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 17, 2026

Last Modified

November 17, 2026

Advisory Details (4)

Auto-updated Nov 20, 2026
Patch available. Sources: github_commit.
GitHub commit

commit ade64619df04 (openssl/openssl)

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

https://github.com/openssl/openssl/commit/ade64619df04056b3e5fd1c1befe9425a7c80eb6
GitHub commit

commit 9a812981b927 (openssl/openssl)

Fix landed in openssl/openssl commit 9a812981b927 — awaiting tagged release

https://github.com/openssl/openssl/commit/9a812981b927c5714b7c2e5d138618105cea2152
GitHub commit

commit 9491b0d9cc79 (openssl/openssl)

Fix landed in openssl/openssl commit 9491b0d9cc79 — awaiting tagged release

https://github.com/openssl/openssl/commit/9491b0d9cc7950af1f3dc89499bd5433b9cd4f43

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 12× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:39 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  2. 2026-11-20 16:37 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-11-20 05:54 UTCEchelonGraph re-scored
  4. 2026-11-20 05:54 UTCVendor advisory
  5. 2026-11-20 05:54 UTCGHSA enrichmentGHSA-r3mj-hq6x-h82q · GitHub severity MODERATE · GitHub CVSS 5.3
  6. 2026-11-19 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-11-17 22:35 UTCEchelonGraph re-scored
  9. 2026-11-17 22:35 UTCGHSA enrichmentGHSA-r3mj-hq6x-h82q · GitHub severity MODERATE · GitHub CVSS 5.3
  10. 2026-11-17 17:29 UTCEchelonGraph re-scoredFirst assessed: 5.3 MEDIUM
  11. 2026-11-17 17:29 UTCGHSA enrichmentGHSA-r3mj-hq6x-h82q
  12. 2026-11-17 17:27 UTCNVD updateCVSS v3 → 5.3 · severity → MEDIUM
  13. 2026-11-17 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-11-17 09:03 UTCENISA EUVD ID recordedEUVD-2026-126929 · Source: ENISA EUVD
  15. 2026-11-17 08:19 UTCEchelonGraph re-scored
  16. 2026-11-17 08:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-35190?
CVE-2026-35190 is a medium-severity vulnerability; its CVE record was published on November 17, 2026. Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client…
When was CVE-2026-35190 made public?
CVE-2026-35190 was made public on November 17, 2026: that is the date its CVE record's CNA, OpenSSL Software Foundation, gives for when the vulnerability was made public. The CVE record itself was published on November 17, 2026. EchelonGraph's copy of the record carries a last-modified date of November 17, 2026; the record at its source may have been updated since.
Is CVE-2026-35190 actively exploited?
CVE-2026-35190 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-35190?
CVE-2026-35190 has a CVSS v3.1 base score of 5.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-35190?
A fix for CVE-2026-35190 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-35190 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-35190

Explore →

Is Your Infrastructure Affected by CVE-2026-35190?

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