cve.bz

CVE-2026-2673 Algorithm Downgrade

6.5 mediumEPSS 0.5%Fix available

Medium (6.5). EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 43rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-03-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-757 Selection of Less-Secure Algorithm During Negotiation (Algorithm Downgrade)
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-2673 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-2673?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-2673?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-2673 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
OpenSSLfrom 3.6.0 before 3.6.2
OpenSSLfrom 3.5.0 before 3.5.6

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13openssl3.5.5-1~deb13u2DEBIAN-CVE-2026-2673
Debian14openssl3.6.2-1DEBIAN-CVE-2026-2673
Ubuntu25.10openssl3.5.3-1ubuntu3.3UBUNTU-CVE-2026-2673
Ubuntu26.04:LTS, 26.10openssl3.5.5-1ubuntu3UBUNTU-CVE-2026-2673
UbuntuPro:22.04:LTSnodejsno fix listedUBUNTU-CVE-2026-2673
Red Hatenterprise_linux:9::appstreamopenssl-perl, openssl-devel, openssl-debuginfo and 2 more1:3.5.5-3.el9_8RHSA-2026:22312
Red Hatenterprise_linux:9::baseosopenssl, openssl-libs, openssl-debuginfo and 2 more1:3.5.5-3.el9_8RHSA-2026:22312
Red Hatenterprise_linux:10.2openssl, openssl-libs, openssl-perl and 4 more1:3.5.5-2.el10_2RHSA-2026:19066
Red Hathummingbird:1openssl, openssl-libs, openssl-perl and 3 more0:3.5.6-0.1.hum1RHSA-2026:7261
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0openssl-33.5.0-160000.7.1SUSE-SU-2026:21186-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0openssl-33.5.0-160000.8.1SUSE-SU-2026:22315-1
SUSELinux Micro 6.2openssl-33.5.0-160000.7.1SUSE-SU-2026:21107-1
SUSELinux Micro 6.2openssl-33.5.0-160000.8.1SUSE-SU-2026:22251-1
openSUSELeap 16.0openssl-33.5.0-160000.7.1openSUSE-SU-2026:20525-1
openSUSELeap 16.0openssl-33.5.0-160000.8.1openSUSE-SU-2026:21005-1
openSUSETumbleweedopenssl-33.5.3-4.1openSUSE-SU-2026:10533-1
AlmaLinux9openssl, openssl-libs, openssl-perl and 1 more1:3.5.5-3.el9_8ALSA-2026:22312
AlmaLinux10openssl, openssl-libs, openssl-perl and 1 more1:3.5.5-2.el10_2.alma.1ALSA-2026:19066
Alpinev3.22, v3.23, v3.24openssl3.5.6-r0ALPINE-CVE-2026-2673
Alpaquita25, streamopenssl3.5.5-r1BELL-CVE-2026-2673
BellSoft Hardened Containers25, streamopenssl3.5.5-r1BELL-CVE-2026-2673

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; the Alpine secdb, CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpine · Alpaquita · BellSoft Hardened Containers.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

The impact of this flaw is limited to the choice of key agreement groups in a specific TLS connection. While a less a preferred key agreement group may allow for a connection to lack post-quantum protection, it is important to know that the connection will still be encrypted with a secure classical cipher and that the degradation of the cipher is limited to the active connection and is not a persistent degradation. Groups which the server operator has disallowed will not be used and it may be the case that the client and server fail to agree upon a key exchange group which would prevent the offending client from constructing a TLS connection.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10openssl-1:3.5.5-2.el10_2Fixed 2026-05-19RHSA-2026:19066
Red Hat Enterprise Linux 9openssl-1:3.5.5-3.el9_8Fixed 2026-06-01RHSA-2026:22312
Red Hat JBoss Core Services 2.4.62.SP4jbcs-httpd24-opensslFixed 2026-06-22RHSA-2026:27201
Red Hat JBoss Web Server 6.2.4openssl.exeFixed 2026-07-22RHSA-2026:43402
Red Hat JBoss Web Server 7.0.0openssl.exeFixed 2026-07-14RHSA-2026:39189
Cert Manager support for Red Hat OpenShift release 1.17cert-manager/jetstack-cert-manager-acmesolver-rhel9:1791371080Fixed 2026-10-13RHSA-2026:82304
Cert Manager support for Red Hat OpenShift release 1.17cert-manager/jetstack-cert-manager-rhel9:1791371069Fixed 2026-10-13RHSA-2026:82304
Cert Manager support for Red Hat OpenShift release 1.17cert-manager/cert-manager-operator-rhel9:1791788287Fixed 2026-10-13RHSA-2026:82322
Cert Manager support for Red Hat OpenShift release 1.17cert-manager/cert-manager-operator-bundle:1791970484Fixed 2026-10-14RHSA-2026:82888
Cert Manager support for Red Hat OpenShift release 1.18cert-manager/jetstack-cert-manager-acmesolver-rhel9:1791459707Fixed 2026-10-13RHSA-2026:82347
Red Hat Enterprise Linux 10openssl-fips-providerNot affected
Red Hat Enterprise Linux 6opensslNot affected
Red Hat Enterprise Linux 6openssl098eNot affected
Red Hat Enterprise Linux 7opensslNot affected
Red Hat Enterprise Linux 7openssl098eNot affected
Red Hat Enterprise Linux 8compat-openssl10Not affected
Red Hat Enterprise Linux 8mingw-opensslNot affected
Red Hat Enterprise Linux 8opensslNot affected
Red Hat Enterprise Linux 9compat-openssl11Not affected
Red Hat Enterprise Linux 9openssl-fips-providerNot affected
6 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-2673.

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-26-134-10Siemens SIMATIC2026-05-12Critical ManufacturingSIMATIC CN 4100none listed

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

Attack patterns (CAPEC)

  • CAPEC-220 Client-Server Protocol Manipulation Severity: Medium
  • CAPEC-606 Weakening of Cellular Encryption Severity: High
  • CAPEC-620 Drop Encryption Level Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON