Skip to main content
Menu
CVEs

CVE

OpenSSL denial of service in TLS key-share handling

CVE-2026-35190EUVD-2026-126929GHSA-R3MJ-HQ6X-H82Q

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N · openssl rates this low

5.3MediumCISA-ADP
Exploited
No known exploitation
Fix
Fixed in 4.1.1, 4.0.4, 3.5.10
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 4.1.1, 4.0.4, 3.5.10.

Published
Last modified
Reference
Last checked
0.12% · 2nd percentile
45/100 · provisional
Low (openssl)
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

Summary

A flaw in OpenSSL's TLS 1.3 key-share handling lets a remote client send a crafted ClientHello that makes the server read past the end of a static array, which can crash the process and cause a denial of service. It affects only servers that set the Suite B certificate flag with TLS 1.3 enabled, a non-default setup, and no memory contents are disclosed.

Written by a model from the sources below. Verify against them.

Original description

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.

cve.now Index

45Pcve.now Index 45 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach20/20Affects OpenSSL (software on nearly every server, desktop or phone)
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 90 if added to CISA KEV
  • Would score about 85 if CISA's SSVC rates exploitation active
  • Would score about 50 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 4.1.1, 4.0.4, 3.5.10.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-35190 (Out-of-Bounds Read in TLS 1.3 Key-Share Processing with Suite B Certificate Flag), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-35190 (entry last updated 2026-11-17):
Affected:
- OpenSSL OpenSSL: from 4.1.0, fixed in 4.1.1; from 4.0.0, fixed in 4.0.4; from 3.5.0, fixed in 3.5.10
Fixed versions: 4.1.1, 4.0.4, 3.5.10.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-35190 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-35190 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://openssl-library.org/news/secadv/20261117.txt
- https://github.com/openssl/openssl/commit/ade64619df04056b3e5fd1c1befe9425a7c80eb6
- https://github.com/openssl/openssl/commit/9a812981b927c5714b7c2e5d138618105cea2152
- https://github.com/openssl/openssl/commit/9491b0d9cc7950af1f3dc89499bd5433b9cd4f43
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-35190
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-35190"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • OpenSSL OpenSSL

    From 4.1.0 · fixed in 4.1.1; From 4.0.0 · fixed in 4.0.4; From 3.5.0 · fixed in 3.5.10

Evidence 6

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

  1. Advisory
  2. Patch
  3. Patch
  4. Patch

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-35190

Is CVE-2026-35190 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-35190?

OpenSSL: from 4.1.0 before 4.1.1; from 4.0.0 before 4.0.4; from 3.5.0 before 3.5.10.Source: cve.now feed data

How do I fix CVE-2026-35190?

Upgrade to a fixed version: 4.1.1, 4.0.4, 3.5.10.Source: cve.now feed data

Why is it rated 5.3 Medium?

CVSS 5.3 scores the worst case. openssl rates it Low.

More CVEs