grpcio is vulnerable to Server-Side Request Forgery (SSRF)
59
Medium Risk
gRPC's default HTTP proxy mapper decides whether to route a destination through a configured proxy by checking the destination hostname against the no_proxy/NO_PROXY environment variable with a simple substring/suffix comparison instead of a boundary-aware host match. A destination hostname that only shares a suffix with a no_proxy entry can match unintentionally, letting a connection meant to go through the proxy bypass it. Bypassing the proxy skips whatever network boundary the operator configured it to enforce, so the connection reaches its destination directly instead of through the intended intermediary. The fix replaces the substring check with boundary-aware hostname comparison so only exact host or full domain-suffix matches are honored.
You are affected if you are using a version that falls within the vulnerable range and you rely on the no_proxy/NO_PROXY environment variable to route selected destinations around an HTTP proxy.
grpcio is vulnerable to Server-Side Request Forgery (SSRF) in versions 1.0.0 - 1.83.1.
Upgrade the grpcio library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.