The issue is related to an integer overflow when decoding chunk sizes that are too big, which can trigger data loss or, in certain cases, "request smuggling" or "desync attacks" if combined with an upstream HTTP proxy that allows larger chunk sizes. This can occur when using hyper for any HTTP/1 purpose, including as a client or server, and consumers send requests or responses that specify a chunk size greater than 18 exabytes. For a possible request smuggling attack to be possible, any upstream proxies must accept a chunk size greater than 64 bits.