Three related things. (a) golang-announce pre-announced a golang.org/x/net/html security fix for "US business hours on Tuesday, October 27", which is tonight in India. It covers multiple CVEs. (b) Overnight (02:40–02:54 IST) the Go security team filed 12 private security issues: CVE-2026-97033…97043 as #82567–#82577, and CVE-2026-97054 as #82563. All are release-blockers with backports on the Go1.27.4 and Go1.26.11 milestones. There's no 1.27.4/1.26.11 pre-announcement yet. (c) The same milestone carries #82536 / CL 854185: Go 1.27 will omit ML-DSA from signature_algorithms_cert. That's the fix decided on #81199 (10-26). Since Go 1.27, middleboxes reset or silently drop Go clients' ClientHellos. Reports name Palo Alto (a rule aimed at an old OpenSSL DoS), F5 BIG-IP and Kaseya/Autotask's edge. #82553 is the silent variant: no RST or alert, just a handshake timeout, isolated to extension 50. ML-DSA stays in signature_algorithms, and Go 1.28 drops signature_algorithms_cert entirely.
go get golang.org/x/net@latest in anything that parses HTML. If some partner endpoints give you unexplained TLS handshake timeouts since moving to 1.27.x, this is probably the cause. Until 1.27.4 ships, build those clients with go1.26.10 or cap MaxVersion at TLS 1.2.