VulertSecurity VulertSecurity

Vulnerability Database · Hex · Package report

grpc: vulnerability history, versions and safety

grpc is a package in the Hex ecosystem. Vulert records 8 vulnerabilities for it across 21 releases, from Jun 2026 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded C1 H3 U4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
8 in the last 12 months

Most recent disclosure 25 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all grpc vulnerabilities

Vulert verdict on grpc 1.0.5 i

Updated on 23 Oct 2026

Good news: 1.0.5, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 8.

Package health score 70/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Not enough data

What to do: Stay on 1.0.5 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.0.5 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.0.5 — unaffected i
  • Vulnerabilities on record 8 over 1 year · 8 in the last year i
  • Latest disclosure 25 Aug 2026 i
  • Highest CVSS 9.2 i
  • With no published fix 0 i
  • Depended on by 7,384,966 packages i
  • Last release 1 month ago i

Version list, release dates, licence and dependants published by hex.pm, 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 grpc, 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.0.5 31 Aug 2026 none — — Details →
1.0.4 15 Aug 2026 none — — Details →
1.0.3 27 Jul 2026 none — — Details →
1.0.2 30 Jun 2026 none — — Details →
1.0.1 23 Jun 2026 none — — Details →
1.0.0 15 Jun 2026 none — — Details →
1.0.0-rc.1 08 Apr 2026 C1 H3 U4 — Yes Details →
0.11.5 14 Nov 2025 C1 H3 U4 — Yes Details →
0.11.4 07 Nov 2025 C1 H3 U4 — Yes Details →
0.11.3 23 Oct 2025 C1 H3 U4 — Yes Details →
0.11.2 16 Oct 2025 C1 H3 U4 — Yes Details →
0.11.1 14 Oct 2025 C1 H3 U4 — Yes Details →
0.11.0 14 Oct 2025 C1 H3 U4 — Yes Details →
0.10.2 12 Jul 2025 C1 H3 U4 — Yes Details →
0.10.1 10 May 2025 C1 H3 U4 — Yes Details →
0.10.0 06 May 2025 C1 H3 U4 — Yes Details →
0.9.0 19 Jul 2024 C1 H3 U4 — Yes Details →
0.8.1 08 Apr 2024 C1 H3 U4 — Yes Details →
0.8.0 06 Apr 2024 C1 H3 U4 — Yes Details →
0.7.0 05 Sep 2023 C1 H2 U3 — Yes Details →
0.6.0 14 Jun 2023 C1 H2 U3 — Yes Details →
0.5.0 27 Jul 2022 C1 H2 U3 — Yes Details →
0.5.0-beta.1 21 Mar 2020 C1 H2 U3 — Yes Details →
0.5.0-beta 24 Dec 2019 C1 H2 U3 — Yes Details →
0.4.0-alpha.2 22 Mar 2019 H1 U1 — Yes Details →
0.4.0-alpha.1 19 Mar 2019 H1 U1 — Yes Details →
0.3.1 07 Dec 2018 H1 U1 — Yes Details →
0.3.0-alpha.2 17 Apr 2018 none — — Details →
0.3.0-alpha.1 24 Mar 2018 none — — Details →
0.3.0-alpha 21 Mar 2018 none — — Details →

All 30 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 8

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

03 Vulnerabilities

Recorded vulnerabilities for grpc

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-48853: Remote Code Execution and Denial of Service in elixir-grpc Package 9.2 critical 1.0.0 15 Jun 2026
CVE-2026-48853: gRPC Erlang Package Vulnerable to Remote Code Execution and Denial of Service 9.2 critical 1.0.0 25 Aug 2026
CVE-2026-48854: Memory Exhaustion Vulnerability in elixir-grpc/grpc Due to Unbounded Request Body Accumulation 8.7 high 1.0.0 15 Jun 2026
CVE-2026-53430: grpc Package Gzip Decompression Bomb Vulnerability 8.7 high 1.0.0 15 Jun 2026
CVE-2026-53430: gRPC Erlang Package Suffers from Unbounded Gzip Decompression Vulnerability 8.7 high 1.0.0 25 Aug 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 grpc

Is grpc safe to use?

Vulert records 8 vulnerabilities for grpc in Hex: 1 critical, 3 high, 0 medium and 0 low, plus 4 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 grpc's Vulert package health score?

Vulert scores grpc 70/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 grpc affected?

No. 1.0.5, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does grpc have?

8 vulnerabilities are recorded for grpc in the Hex ecosystem: 1 critical, 3 high, 0 medium and 0 low, plus 4 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 grpc vulnerabilities disclosed?

8 vulnerabilities were recorded for grpc in the last 12 months, and the oldest entry in this database dates to 15 Jun 2026. 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 grpc 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 grpc for upcoming vulnerabilities?

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