CVE-2026-35190: Out-of-Bounds Read in TLS 1.3 Key-Share Processing with Suite B Certificate Flag

Published Nov 17, 2026
·
Updated

Issue summary: A server configured with the Suite B certificate flag through SSLCTXsetcertflags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supportedgroups and keyshare 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: tls1getgrouptuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tlsparsectoskeyshare() 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 SSLCTXsetcertflags() with SSLCERTFLAGSUITEB128LOS and leave TLS 1.3 enabled are affected. The openssl sserver -suiteB128 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.

Other sources

Out-of-Bounds Read in TLS 1.3 Key-Share Processing with Suite B Certificate Flag

— Debian

Affected Software

5 affected components
OpenSSL OpenSSL
debian/openssl*
debian/openssl*
debian/openssl*
debian/openssl<=3.0.20-1~deb12u2, <=3.0.22-1~deb12u2, <=3.5.7-1~deb13u2, <=3.5.7-1~deb13u3, <=3.6.5-1

Event History

Nov 17, 2026
CVE Published
via MITRE·08:15 AM
Data Sourced
via MITRE·08:15 AM
DescriptionWeakness
Data Sourced
via NVD·09:17 AM
DescriptionSeverityWeakness
Data Sourced
via OSV·04:00 PM
Affected Software

Frequently Asked Questions

1

Are default OpenSSL server configurations affected?

No. The issue affects only applications that enable TLS 1.3 and explicitly set the Suite B certificate flag using SSL_CTX_set_cert_flags().

2

What must a remote client send to trigger the faulty processing?

The client must send a ClientHello in which both supported_groups and key_share contain no Suite B group. No authentication or prior connection state is described as necessary.

3

What is the practical impact of a successful trigger?

The server reads past the end of a static array. The out-of-bounds values are not returned to the client, but sanitizer-enabled builds or systems using hardened allocators may crash, causing denial of service.

4

What can be done before a patch is available?

Where operationally feasible, avoid setting the Suite B certificate flag or disable TLS 1.3, since both settings are required for the affected code path. Audit application code and configuration for calls to SSL_CTX_set_cert_flags() that enable the Suite B flag.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203