CVE-2026-1677

published 11 May 2026 · updated 15 Oct 2026

net: TLS 1.2 connections allowed on TLS 1.3 sockets

5.3MediumCVSS 5.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 4.4.0.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
zephyrproject-rtos<4.4.04.4.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-1677 severity on Zeptric[![CVE-2026-1677](https://zeptric.io/badge/cve/CVE-2026-1677.svg)](https://zeptric.io/cve/CVE-2026-1677)