CVE-2026-1677CWE-757

CVE-2026-1677

Medium · published May 11, 2026

CVSS v3.1
5.3
EPSS
0%
Percentile
14.7
In the wild
Unconfirmed
What it is

Zephyr sockets created with `IPPROTO_TLS_1_3` can still negotiate a TLS 1.2 connection when both TLS versions are enabled in Kconfig, because the socket-level protocol selection is not propagated to mbedTLS (e.g. via `mbedtls_ssl_conf_min_tls_version`). The ClientHello advertises both versions and the peer can establish TLS 1.2, so applications that assumed `IPPROTO_TLS_1_3` enforces TLS 1.3 may silently use TLS 1.2 and remain exposed to TLS 1.2-specific weaknesses. As a workaround, the `TLS_CIPHERSUITE_LIST` socket option can be restricted to TLS 1.3-only cipher suites.

The record
Technical detail
CVSS v3.1
5.3 · MEDIUM
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CVSS v4.0
Not supplied
EPSS
0.00243 · 14.7th percentile
Weakness
CWE-757 · Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade')
Published
2026-05-11T10:16Z
Affected products (1)
ProductVersionsFixed in
zephyrproject/zephyr≤ 4.3.0—
References (2)
EPSS history
Timeline
  • 11 MAY 05:52Z
    net: TLS 1.2 connections allowed on TLS 1.3 sockets
    cvelistv5