The Tokio rate limit vulnerability involves the `tonic_middleware::IpKeyExtractor` component, which is intended to rate limit gRPC requests by client IP address. However, in versions 0.5.0 through 0.11.0, it relies on client-supplied `x-forwarded-for` and `x-real-ip` headers to determine the client IP, allowing attackers to bypass per-IP rate limits by manipulating these headers. Version 0.11.1 fixes this by using server-supplied connection information instead of untrusted headers. Deployments behind trusted proxies can opt-in to a new extractor that safely reads forwarding headers. Without upgrading, mitigations include using a custom key extractor or restricting backend access to trusted proxies that sanitize forwarding headers.