grpcio vulnerabilities
HTTP/2-based RPC framework
- Registry
- PyPI
- Latest
- 1.85.3
- License
- Apache-2.0
6 known advisories
The latest version, 1.85.3, is not affected by any of them. Projects on older versions may be.
pip install 'grpcio>=1.85.3'Is your project on an affected grpcio?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for grpcio
Denial of Service Vulnerability in gRPC TCP Server (Posix-compatible platforms)
- Affected
- >=1.55.0 <1.55.3 · >=1.54.0 <1.54.3 · >=1.53.0 <1.53.2
- Fixed in
- 1.53.2, 1.54.3, 1.55.3
Excessive Iteration in gRPC
- Affected
- <1.53.2 · >=1.54.0 <1.54.3 · >=1.55.0 <1.55.2 · >=1.56.0 <1.56.2
- Fixed in
- 1.53.2, 1.54.3, 1.55.2, 1.56.2
gRPC Reachable Assertion issue
- Affected
- >=1.51.0 <1.53.0
- Fixed in
- 1.53.0
gRPC connection termination issue
- Affected
- >=1.53.0 <1.53.1 · >=1.54.0 <1.54.2
- Fixed in
- 1.53.1, 1.54.2
Connection confusion in gRPC
- Affected
- >=1.53.0 <1.53.1 · >=1.54.0 <1.54.2
- Fixed in
- 1.53.1, 1.54.2
No summary published
- Affected
- <1.3.0
- Fixed in
- 1.3.0
Is your grpcio version vulnerable?
- grpcio 1.85No known advisories in 1.85.3
- grpcio 1.84No known advisories in 1.84.2
- grpcio 1.83No known advisories in 1.83.2
- grpcio 1.82No known advisories in 1.82.3
- grpcio 1.81No known advisories in 1.81.2
- grpcio 1.80No known advisories in 1.80.1
- grpcio 0.152 advisories in 0.15.0
- grpcio 0.142 advisories in 0.14.0
- grpcio 0.132 advisories in 0.13.1
Which of your client projects still run an old grpcio?
NPMscan reads the requirements.txt, poetry.lock, uv.lock and Pipfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other PyPI packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the PyPI registry.