Invoking Encrypted Client Hello privacy leak in crypto/tls

These records connect through source-stated identifiers. Shared identifiers or dates alone do not establish shared exposure, root cause or applicability.

CVE-2026-42505 · Microsoft / collected KEV context

EUVD-2026-42317

GHSA-ff52-ph69-cf7x

GO-2026-5856

BIT-golang-2026-42505

cve-program · CVE-2026-42505

• https://go.dev/cl/775960
• https://go.dev/issue/79282
• https://groups.google.com/g/golang-announce/c/OrmQE_Yp5Sc
• https://pkg.go.dev/vuln/GO-2026-5856

euvd · EUVD-2026-42317

• https://go.dev/cl/775960
• https://go.dev/issue/79282
• https://groups.google.com/g/golang-announce/c/OrmQE_Yp5Sc
• https://pkg.go.dev/vuln/GO-2026-5856

nvd · CVE-2026-42505

• https://go.dev/cl/775960
• https://go.dev/issue/79282
• https://groups.google.com/g/golang-announce/c/OrmQE_Yp5Sc
• https://pkg.go.dev/vuln/GO-2026-5856

osv · GO-2026-5856

• https://go.dev/cl/775960
• https://go.dev/issue/79282
• https://groups.google.com/g/golang-announce/c/OrmQE_Yp5Sc

• Handshakes which used Encrypted Client Hello could be de-anonymized by a passive network observer due to a disclosure of pre-shared key identities in the unencrypted client hello. · Advisory content revised · 1 Nov 2026