RUSTSEC-2026-0584: gRPC `IpKeyExtractor` keys on client-supplied forwarding headers

Medium CVSS 5.3

OSV id
RUSTSEC-2026-0584
Also known as
GHSA-r5c9-r265-ccg3
Published
Last modified

Affected packages

PackageAffected versionsFixed in
tokio-rate-limit
Cargo
>= 0.5.0, < 0.11.1 0.11.1

How to fix it

Upgrade tokio-rate-limit to 0.11.1 or later.

cargo update -p tokio-rate-limit --precise 0.11.1
  • If it is an indirect dependency, `cargo update -p` still works; if a parent crate pins an older version, upgrade that crate.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

Not sure whether your project uses an affected version? Check your lockfile below for free.

Details

tonic_middleware::IpKeyExtractor is documented as rate limiting gRPC requests by client IP address, but on a standard tonic server it keys on client-supplied x-forwarded-for and x-real-ip headers. In 0.5.0–0.9.1, the extractor reads those headers directly; in 0.10.0–0.11.0, it first checks for a bare std::net::SocketAddr request extension—which tonic::transport::Server never supplies, as it provides TcpConnectInfo instead—and falls back to the same headers. Direct clients can therefore choose their rate-limit key to bypass per-IP rate limits and increase the number of tracked keys; without forwarding headers, 0.5.0–0.9.1 allow requests without limiting them and 0.10.0–0.11.0 reject them by default unless .fail_open() is enabled.

Applications are affected if they use GrpcRateLimitLayer with IpKeyExtractor (the tonic-support feature). The HTTP middleware's IpKeyExtractor reads ConnectInfo<SocketAddr> and is not affected.

Version 0.11.1 fixes IpKeyExtractor to honor a server-supplied SocketAddr override first and then read the TCP peer address from tonic's TcpConnectInfo (which tonic::transport::Server attaches to plaintext connections and connections using its built-in TLS), without ever reading forwarding headers. Deployments behind a trusted proxy can use the new opt-in ForwardedIpKeyExtractor, which reads a single configured header (x-forwarded-for or x-real-ip) and is only correct when that proxy sets the header as documented.

If you cannot upgrade to 0.11.1, use a custom key extractor that reads the peer IP from tonic's connection information for the transport in use (including TLS) and rejects requests without a verified peer address before invoking the limiter, or restrict backend access to a trusted proxy that strips all incoming x-forwarded-for and x-real-ip fields and sets one x-forwarded-for value to the verified client IP on every request.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: RustSec Advisory Database via OSV.dev (CC0 1.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.