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.
Metrics
Affected Vendors & Products
References
History
Mon, 11 May 2026 07:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Zephyrproject-rtos
Zephyrproject-rtos zephyr |
|
| Vendors & Products |
Zephyrproject-rtos
Zephyrproject-rtos zephyr |
Mon, 11 May 2026 06:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | net: TLS 1.2 connections allowed on TLS 1.3 sockets | |
| Weaknesses | CWE-757 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: zephyr
Published: 2026-05-11T05:52:12.140Z
Updated: 2026-05-11T16:31:22.202Z
Reserved: 2026-01-30T05:38:22.811Z
Link: CVE-2026-1677
No data.
Status : Received
Published: 2026-05-11T06:16:08.683
Modified: 2026-05-11T06:16:08.683
Link: CVE-2026-1677
No data.