VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

grpcio: vulnerability history, versions and safety

grpcio is a package in the PyPI ecosystem. Vulert records 7 vulnerabilities for it across 120 releases, from Apr 2017 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded H1 U6
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
5 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all grpcio vulnerabilities

Vulert verdict on grpcio 1.84.1 i

Updated on 23 Oct 2026

Action needed: 1.84.1 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 79/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 1.84.1 — affected i
  • Vulnerabilities on record 7 over 9 years · 5 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 45,393 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for grpcio, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.84.1 22 Oct 2026 U1 Apache-2.0 Yes Details →
1.85.0rc1 09 Oct 2026 U1 Apache-2.0 Yes Details →
1.84.0 14 Sep 2026 U1 Apache-2.0 Yes Details →
1.84.0rc2 09 Sep 2026 U1 Apache-2.0 Yes Details →
1.84.0rc1 08 Sep 2026 U1 Apache-2.0 Yes Details →
1.83.1 28 Aug 2026 U1 Apache-2.0 Yes Details →
1.82.2 28 Aug 2026 U1 Apache-2.0 Yes Details →
1.83.0 23 Jul 2026 U1 Apache-2.0 Yes Details →
1.83.0rc1 13 Jul 2026 U1 Apache-2.0 Yes Details →
1.82.1 08 Jul 2026 U1 Apache-2.0 Yes Details →
1.82.0 06 Jul 2026 U1 Apache-2.0 Yes Details →
1.82.0rc2 29 Jun 2026 U1 Apache-2.0 Yes Details →
1.82.0rc1 17 Jun 2026 U1 Apache-2.0 Yes Details →
1.81.1 11 Jun 2026 U1 Apache-2.0 Yes Details →
1.81.0 01 Jun 2026 U1 Apache-2.0 Yes Details →
1.81.0rc1 18 May 2026 U1 Apache-2.0 Yes Details →
1.80.0 30 Mar 2026 U1 Apache-2.0 Yes Details →
1.80.0rc1 17 Mar 2026 U1 Apache-2.0 Yes Details →
1.78.1 20 Feb 2026 U1 Apache-2.0 Yes Details →
1.78.0 06 Feb 2026 U1 Apache-2.0 Yes Details →
1.78.0rc2 16 Jan 2026 U1 Apache-2.0 Yes Details →
1.76.0 21 Oct 2025 U1 Apache-2.0 Yes Details →
1.76.0rc1 03 Oct 2025 U1 Apache-2.0 Yes Details →
1.75.1 26 Sep 2025 U1 Apache-2.0 Yes Details →
1.75.0 16 Sep 2025 U1 Apache-2.0 Yes Details →
1.75.0rc1 27 Aug 2025 U1 Apache-2.0 Yes Details →
1.74.0 24 Jul 2025 U1 Apache-2.0 Yes Details →
1.74.0rc1 14 Jul 2025 U1 Apache-2.0 Yes Details →
1.71.2 28 Jun 2025 U1 Apache-2.0 Yes Details →
1.72.2 26 Jun 2025 U1 Apache-2.0 Yes Details →
1.73.1 26 Jun 2025 U1 Apache-2.0 Yes Details →
1.73.0 09 Jun 2025 U1 Apache-2.0 Yes Details →
1.72.1 02 Jun 2025 U1 Apache-2.0 Yes Details →
1.73.0rc1 28 May 2025 U1 Apache-2.0 Yes Details →
1.72.0 25 Apr 2025 U1 Apache-2.0 Yes Details →
1.72.0rc1 08 Apr 2025 U1 Apache-2.0 Yes Details →
1.71.0 10 Mar 2025 U1 Apache-2.0 Yes Details →
1.71.0rc2 24 Feb 2025 U1 Apache-2.0 Yes Details →
1.70.0 23 Jan 2025 U1 Apache-2.0 Yes Details →
1.70.0rc1 15 Jan 2025 U1 Apache-2.0 Yes Details →
1.69.0 05 Jan 2025 U1 Apache-2.0 Yes Details →
1.69.0rc1 17 Dec 2024 U1 Apache-2.0 Yes Details →
1.68.1 02 Dec 2024 U1 Apache-2.0 Yes Details →
1.68.0 16 Nov 2024 U1 Apache-2.0 Yes Details →
1.68.0rc1 31 Oct 2024 U1 Apache-2.0 Yes Details →
1.67.1 29 Oct 2024 U1 Apache-2.0 Yes Details →
1.67.0 16 Oct 2024 U1 Apache-2.0 Yes Details →
1.66.2 28 Sep 2024 U1 Apache-2.0 Yes Details →
1.67.0rc1 20 Sep 2024 U1 Apache-2.0 Yes Details →
1.66.1 28 Aug 2024 U1 Apache-2.0 Yes Details →
1.66.0 22 Aug 2024 U1 Apache-2.0 Yes Details →
1.65.5 17 Aug 2024 U1 Apache-2.0 Yes Details →
1.66.0rc5 16 Aug 2024 U1 Apache-2.0 Yes Details →
1.66.0rc3 08 Aug 2024 U1 Apache-2.0 Yes Details →
1.58.3 06 Aug 2024 U1 Apache-2.0 Yes Details →
1.59.5 06 Aug 2024 U1 Apache-2.0 Yes Details →
1.60.2 06 Aug 2024 U1 Apache-2.0 Yes Details →
1.61.3 06 Aug 2024 U1 Apache-2.0 Yes Details →
1.62.3 06 Aug 2024 U1 Apache-2.0 Yes Details →
1.63.2 06 Aug 2024 U1 Apache-2.0 Yes Details →
1.64.3 06 Aug 2024 U1 Apache-2.0 Yes Details →
1.66.0rc2 02 Aug 2024 U1 Apache-2.0 Yes Details →
1.66.0rc1 02 Aug 2024 U1 Apache-2.0 Yes Details →
1.65.4 02 Aug 2024 U1 Apache-2.0 Yes Details →
1.65.2 31 Jul 2024 U1 Apache-2.0 Yes Details →
1.65.1 18 Jul 2024 U1 Apache-2.0 Yes Details →
1.65.0 11 Jul 2024 U1 Apache-2.0 Yes Details →
1.65.0rc2 27 Jun 2024 U1 Apache-2.0 Yes Details →
1.65.0rc1 18 Jun 2024 U1 Apache-2.0 Yes Details →
1.64.1 03 Jun 2024 U1 Apache-2.0 Yes Details →
1.64.0 20 May 2024 U1 Apache-2.0 Yes Details →
1.64.0rc1 08 May 2024 U1 Apache-2.0 Yes Details →
1.63.0 30 Apr 2024 U1 Apache-2.0 Yes Details →
1.63.0rc2 19 Apr 2024 U1 Apache-2.0 Yes Details →
1.62.2 18 Apr 2024 U1 Apache-2.0 Yes Details →
1.63.0rc1 15 Apr 2024 U1 Apache-2.0 Yes Details →
1.62.1 08 Mar 2024 U1 Apache-2.0 Yes Details →
1.62.0 21 Feb 2024 U1 Apache-2.0 Yes Details →
1.62.0rc1 16 Feb 2024 U1 Apache-2.0 Yes Details →
1.60.1 01 Feb 2024 U1 Apache-2.0 Yes Details →
1.60.0 07 Dec 2023 U1 Apache-2.0 Yes Details →
1.59.3 17 Nov 2023 U1 Apache-2.0 Yes Details →
1.60.0rc1 14 Nov 2023 U1 Apache-2.0 Yes Details →
1.59.2 30 Oct 2023 U1 Apache-2.0 Yes Details →
1.59.0 29 Sep 2023 U1 Apache-2.0 Yes Details →
1.59.0rc1 27 Sep 2023 U1 Apache-2.0 Yes Details →
1.58.0 07 Sep 2023 U1 Apache-2.0 Yes Details →
1.58.0rc1 25 Aug 2023 U1 Apache-2.0 Yes Details →
1.57.0 10 Aug 2023 U1 Apache-2.0 Yes Details →
1.53.2 02 Aug 2023 U1 Apache-2.0 Yes Details →
1.54.3 02 Aug 2023 U1 Apache-2.0 Yes Details →
1.55.3 01 Aug 2023 U1 Apache-2.0 Yes Details →
1.57.0rc1 26 Jul 2023 U1 Apache-2.0 Yes Details →
1.56.2 19 Jul 2023 U1 Apache-2.0 Yes Details →
1.56.0 22 Jun 2023 U1 Apache-2.0 Yes Details →
1.56.0rc2 13 Jun 2023 U1 Apache-2.0 Yes Details →
1.55.0 22 May 2023 U2 Apache-2.0 Yes Details →
1.54.2 12 May 2023 U2 Apache-2.0 Yes Details →
1.53.1 12 May 2023 H1 U2 Apache-2.0 Yes Details →
1.55.0rc1 01 May 2023 U1 Apache-2.0 Yes Details →
1.54.0 18 Apr 2023 U4 — Yes Details →
1.54.0rc1 05 Apr 2023 U1 — Yes Details →
1.53.0 27 Mar 2023 H1 U4 — Yes Details →
1.53.0rc2 14 Mar 2023 H1 U2 — Yes Details →
1.47.5 28 Feb 2023 H1 U1 — Yes Details →
1.51.3 21 Feb 2023 H1 U2 — Yes Details →
1.52.0 06 Feb 2023 H1 U2 — Yes Details →
1.52.0rc1 19 Jan 2023 H1 U2 — Yes Details →
1.51.1 29 Nov 2022 H1 U2 — Yes Details →
1.51.0 21 Nov 2022 H1 U2 — Yes Details →
1.51.0rc1 14 Nov 2022 H1 U1 — Yes Details →
1.50.0 18 Oct 2022 H1 U1 — Yes Details →
1.50.0rc1 03 Oct 2022 H1 U1 — Yes Details →
1.49.1 22 Sep 2022 H1 U1 — Yes Details →
1.48.2 22 Sep 2022 H1 U1 — Yes Details →
1.47.2 22 Sep 2022 H1 U1 — Yes Details →
1.46.5 22 Sep 2022 H1 U1 — Yes Details →
1.49.0 15 Sep 2022 H1 U1 — Yes Details →
1.48.1 01 Sep 2022 H1 U1 — Yes Details →
1.49.0rc3 01 Sep 2022 H1 U1 — Yes Details →

The newest 120 of 283 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2023 1
  • 2026 5

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 5 of the 7 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for grpcio

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Excessive Iteration in gRPC 7.5 high 1.53.2 09 Aug 2023
CVE-2023-33953: gRPC Excessive Iteration Vulnerability Leading to Denial of Service 7.5 high 1.53.2 07 Jul 2026
CVE-2023-1428: gRPC Reachable Assertion Issue in grpcio Package 7.5 high 1.53.0 07 Jul 2026
CVE-2023-4785: gRPC TCP Server Denial of Service Vulnerability 7.5 high 1.55.3 07 Jul 2026
CVE-2023-32731: gRPC Connection Confusion Vulnerability Leading to Information Leak 7.4 high 1.53.1 07 Jul 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About grpcio

Is grpcio safe to use?

Vulert records 7 vulnerabilities for grpcio in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 6 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is grpcio's Vulert package health score?

Vulert scores grpcio 79/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of grpcio affected?

Yes. 1.84.1, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

How many vulnerabilities does grpcio have?

7 vulnerabilities are recorded for grpcio in the PyPI ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 6 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new grpcio vulnerabilities disclosed?

5 vulnerabilities were recorded for grpcio in the last 12 months, and the oldest entry in this database dates to 30 Apr 2017. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of grpcio are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor grpcio for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the grpcio version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.