Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-2673

openssl: OpenSSL TLS 1.3 server may choose unexpected key agreement group

Overview

Published
13 Mar 2026
Modified
17 Jun 2026
Medium CVE
3 Registry packages
34 OS packages
17 Linux distributions
Yes Fix available

Description

Issue summary: An OpenSSL TLS 1.3 server may fail to negotiate the expected
preferred key exchange group when its key exchange group configuration includes
the default by using the 'DEFAULT' keyword.

Impact summary: A less preferred key exchange may be used even when a more
preferred group is supported by both client and server, if the group
was not included among the client's initial predicated keyshares.
This will sometimes be the case with the new hybrid post-quantum groups,
if the client chooses to defer their use until specifically requested by
the server.

If an OpenSSL TLS 1.3 server's configuration uses the 'DEFAULT' keyword to
interpolate the built-in default group list into its own configuration, perhaps
adding or removing specific elements, then an implementation defect causes the
'DEFAULT' list to lose its 'tuple' structure, and all server-supported groups
were treated as a single sufficiently secure 'tuple', with the server not
sending a Hello Retry Request (HRR) even when a group in a more preferred tuple
was mutually supported.

As a result, the client and server might fail to negotiate a mutually supported
post-quantum key agreement group, such as 'X25519MLKEM768', if the client's
configuration results in only 'classical' groups (such as 'X25519' being the
only ones in the client's initial keyshare prediction).

OpenSSL 3.5 and later support a new syntax for selecting the most preferred TLS
1.3 key agreement group on TLS servers. The old syntax had a single 'flat'
list of groups, and treated all the supported groups as sufficiently secure.
If any of the keyshares predicted by the client were supported by the server
the most preferred among these was selected, even if other groups supported by
the client, but not included in the list of predicted keyshares would have been
more preferred, if included.

The new syntax partitions the groups into distinct 'tuples' of roughly
equivalent security. Within each tuple the most preferred group included among
the client's predicted keyshares is chosen, but if the client supports a group
from a more preferred tuple, but did not predict any corresponding keyshares,
the server will ask the client to retry the ClientHello (by issuing a Hello
Retry Request or HRR) with the most preferred mutually supported group.

The above works as expected when the server's configuration uses the built-in
default group list, or explicitly defines its own list by directly defining the
various desired groups and group 'tuples'.

No OpenSSL FIPS modules are affected by this issue, the code in question lies
outside the FIPS boundary.

OpenSSL 3.6 and 3.5 are vulnerable to this issue.

OpenSSL 3.6 users should upgrade to OpenSSL 3.6.2 once it is released.
OpenSSL 3.5 users should upgrade to OpenSSL 3.5.6 once it is released.

OpenSSL 3.4, 3.3, 3.0, 1.0.2 and 1.1.1 are not affected by this issue.

Source: OX vulnerability database

Severity

6.5 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Weakness: CWE-757

Affected packages · 3

Packages affected by CVE-2026-2673
EcosystemPackageVulnerableFixed in
Julia AppBundler >=1.0.0, <1.0.1 1.0.1
Julia Openresty_jll >=1.29.203+0 No fix yet
Julia OpenSSL_jll >=3.5.0+0, <3.5.6+0 3.5.6+0

Open a package to see all its vulnerabilities.

Operating systems · 38 fixes

Red Hat 3 releases · 3 packages

affected 3 eol 3 fixed 1
openssl-exe jbcs-httpd24-openssl openssl
Red Hat fixes for CVE-2026-2673
ReleasePackageFixed in
7 openssl-exe affected
7 jbcs-httpd24-openssl eol
8 openssl-exe affected
8 jbcs-httpd24-openssl eol
9 openssl-exe affected
9 jbcs-httpd24-openssl eol

1 more row

SUSE Linux Enterprise 2 releases · 3 packages

fixed 4
nodejs24 libopenssl-devel libopenssl-3-devel
SUSE Linux Enterprise fixes for CVE-2026-2673
ReleasePackageFixed inAdvisory
15.7 nodejs24 +3 24.18.1-150700.15.18.1 SUSE-SU-2026:3835-1
15.7 libopenssl-devel +2 3.5.0-150700.3.4.1 SUSE-SU-2026:3835-1
15.7 libopenssl-3-devel +5 3.5.0-150700.5.45.2 SUSE-SU-2026:3835-1
16.0 libopenssl-3-devel +6 3.5.0-160000.7.1 SUSE-SU-2026:21186-1

SUSE Linux Enterprise Micro 1 release · 1 package

fixed 1
libopenssl-3-devel
SUSE Linux Enterprise Micro fixes for CVE-2026-2673
ReleasePackageFixed inAdvisory
6.2 libopenssl-3-devel +3 3.5.0-160000.7.1 SUSE-SU-2026:21107-1

alma 1 release · 1 package

fixed 1
openssl
alma fixes for CVE-2026-2673
ReleasePackageFixed in
9 openssl +3 1:3.5.5-3.el9_8

alpine 4 releases · 1 package

fixed 4
openssl
alpine fixes for CVE-2026-2673
ReleasePackageFixed in
3.22 openssl 3.5.6-r0
3.23 openssl 3.5.6-r0
3.24 openssl 3.5.6-r0
edge openssl 3.5.6-r0

amazon linux 1 release · 1 package

fixed 1
openssl
amazon linux fixes for CVE-2026-2673
ReleasePackageFixed in
2023 openssl +10 1:3.5.5-1.amzn2023.0.3

chainguard 1 release · 4 packages

not affected 1 fixed 3
openssl-provider-fips-3-6-0 openssl-3-5 openssl libcrypto3-2-34
chainguard fixes for CVE-2026-2673
ReleasePackageFixed in
openssl-provider-fips-3-6-0 not affected
openssl-3-5 3.5.6-r0
openssl 3.6.1-r3
libcrypto3-2-34 3.6.2-r0

debian 2 releases · 1 package

fixed 2
openssl
debian fixes for CVE-2026-2673
ReleasePackageFixed in
13 openssl 3.5.5-1~deb13u2
14 openssl 3.6.2-1

echo 1 release · 1 package

fixed 1
openssl
echo fixes for CVE-2026-2673
ReleasePackageFixed in
openssl 3.5.5-1~deb13u2

minimos 1 release · 1 package

fixed 1
openssl
minimos fixes for CVE-2026-2673
ReleasePackageFixed in
openssl 3.5.6-r0

openSUSE 1 release · 1 package

fixed 1
libopenssl-3-devel
openSUSE fixes for CVE-2026-2673
ReleasePackageFixed inAdvisory
Tumbleweed libopenssl-3-devel +9 3.5.3-4.1 openSUSE-SU-2026:10533-1

openSUSE Leap 1 release · 1 package

fixed 1
libopenssl-3-devel
openSUSE Leap fixes for CVE-2026-2673
ReleasePackageFixed inAdvisory
16.0 libopenssl-3-devel +6 3.5.0-160000.7.1 openSUSE-SU-2026:20525-1

root.io alpine 1 release · 1 package

fixed 1
rootio-openssl
root.io alpine fixes for CVE-2026-2673
ReleasePackageFixed in
3.23 rootio-openssl 3.5.6-r0

seal Red Hat 3 releases · 1 package

fixed 5
openssl
seal Red Hat fixes for CVE-2026-2673
ReleasePackageFixed in
7 openssl +1 1:1.0.2k-25.el7_9+sp999
7 openssl +1 1:1.0.2k-26.el7_9+sp999
8 openssl +1 1:1.1.1k-14.el8_6+sp999
8 openssl +1 1:1.1.1k-6.el8_5+sp999
9 openssl +1 1:3.2.2-6.el9_5+sp999

seal debian 1 release · 1 package

fixed 1
openssl
seal debian fixes for CVE-2026-2673
ReleasePackageFixed in
openssl +1 3.5.4-1~deb13u1+sp999

ubuntu 2 releases · 2 packages

affected 1 fixed 1
nodejs openssl
ubuntu fixes for CVE-2026-2673
ReleasePackageFixed in
22.04 nodejs affected
26.04 openssl 3.5.5-1ubuntu3

wolfi 1 release · 1 package

fixed 1
openssl
wolfi fixes for CVE-2026-2673
ReleasePackageFixed in
openssl 3.6.1-r3

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.