A common way to let GET handlers serve HEAD is a wrapper that does if r.Method == http.MethodHead { r.Method = http.MethodGet }. The reporter's program sends HEAD /a then GET /b on one connection and gets back a HEAD-framed header (Content-Length: 10) followed by body of /a, then the /b response, all on a connection the server keeps open. A client stops reading a HEAD response at its header, so those stray bytes become the start of what it parses as the next response. The cause: CL 847311 (the CONNECT desync fix for #81744, Go 1.28 only) made chunkWriter.writeHeader frame by the method as read off the wire, but chunkWriter.Write, response.ReadFrom and shouldReuseConnection still look at the handler-mutated w.req.Method. The same applies to the protocol version: a handler that bumps an HTTP/1.0 request to 1.1 gets a chunked 1.1 response sent to a 1.0 client on a kept-open connection. CL 858982 ("frame HTTP/1 server responses by the request as read", #82861) records the method and HTTP/1.1-ness when the response is created and frames everything by those. It isn't labelled as a security issue and has no milestone yet.
r.Method (or r.Proto*), and have HEAD handling call the GET handler with a cloned request or a body-discarding ResponseWriter instead of mutating the request. Watch #82853 for a backport decision.