RUSTSEC-2026-0584

Source
https://rustsec.org/advisories/RUSTSEC-2026-0584
Import Source
https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2026-0584.json
JSON Data
https://api.osv.dev/v1/vulns/RUSTSEC-2026-0584
Aliases
  • GHSA-r5c9-r265-ccg3
Published
2026-11-19T12:00:00Z
Modified
2026-11-20T13:00:02Z
Severity
  • 5.3 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L CVSS Calculator
Summary
gRPC `IpKeyExtractor` keys on client-supplied forwarding headers
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.

Database specific
{
    "license": "CC0-1.0"
}
References

Affected packages

crates.io / tokio-rate-limit

Package

Name
tokio-rate-limit
View open source insights on deps.dev
Purl
pkg:cargo/tokio-rate-limit

Affected ranges

Type
SEMVER
Events
Introduced
0.5.0
Fixed
0.11.1

Ecosystem specific

{
    "affected_functions": null,
    "affects": {
        "arch": [],
        "functions": [
            "tokio_rate_limit::tonic_middleware::IpKeyExtractor::extract"
        ],
        "os": []
    }
}

Database specific

categories
[
    "denial-of-service"
]
cvss
"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
informational
null
source
"https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2026-0584.json"