CVE-2026-1677

The record

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 packages

Related vulnerabilities

• CVE-2026-89177 WeenyGenius, a computer lab management system by Howyar Technologies, has a Use of… CWE-757
• CVE-2026-59293 Unless the application explicitly raises smbMinVersion, the jCIFS client will negotiate… CWE-757
• CVE-2026-72889 Net::OAuth versions before 0.33 for Perl allow the sender to choose the signature… CWE-757
• CVE-2026-72887 Net::OAuth::Client versions before 0.32 for Perl allow the service provider to silently… CWE-757
• CVE-2026-55953 The Erlang/OTP ssl TLS 1.2 (and earlier) and DTLS client does not verify that the cipher… CWE-757
• CVE-2026-54780 CoreWCF is a port of the service side of Windows Communication Foundation (WCF) to .NET… CWE-757
• CVE-2026-54291 pgjdbc is an open source postgresql JDBC Driver. CWE-757
• CVE-2026-6092 When HAVE_ENCRYPT_THEN_MAC is configured, the implementation could fall back to… CWE-757