net: TLS 1.2 connections allowed on TLS 1.3 sockets (zephyrproject-rtos Zephyr)

CVE-2026-1677
MEDIUM 5.3

At a glance

Source
NVD
EPSS
EPSS 0.24 % · percentile 16 ()
State
PUBLISHED
Published
Updated
Assigner
zephyr
NVD status
Analyzed

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.

Weaknesses (CWE)

  • CWE-757 — Selection of Less-Secure Algorithm During Negotiation

References

Scores

VersionScoreVectorScored by
CVSS 3.1MEDIUM 5.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:Nzephyr
CVSS 3.1MEDIUM 5.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NNVD · vulnerabilities@zephyrproject.org (Secondary)

European references

Affected configurations (NVD CPE)

Affected products

ProductVersions
zephyrproject-rtos · Zephyraffected * < 4.4.0

Sources

SourceLicence
CVE List (CVEProject cvelistV5)CVE Program Terms of Use
EPSS (FIRST.org)FIRST — attribution requested
ENISA EUVDENISA — reproduction authorised, source acknowledged
NVD (NIST) via fkie-cad/nvd-json-data-feedsPublic domain — this product uses data from the NVD API but is not endorsed or certified by the NVD