VulertSecurity VulertSecurity

Vulnerability Database · Hex · Package report

protobuf: vulnerability history, versions and safety

protobuf is a package in the Hex ecosystem. Vulert records 2 vulnerabilities for it across 12 releases, from Jul 2026 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 09 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all protobuf vulnerabilities

Vulert verdict on protobuf 0.17.1 i

Updated on 22 Oct 2026

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

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

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

  • Current release 0.17.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 09 Oct 2026 i
  • Highest CVSS 8.2 i
  • With no published fix 0 i
  • Depended on by 25,141,731 packages i
  • Last release this month 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 protobuf, 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
0.17.1 09 Oct 2026 none — — Details →
0.17.0 08 Jun 2026 U1 — Yes Details →
0.16.1 04 Jun 2026 U1 — Yes Details →
0.16.0 09 Jan 2026 H1 U1 — Yes Details →
0.15.0 22 Jul 2025 H1 U1 — Yes Details →
0.14.1 19 Feb 2025 H1 U1 — Yes Details →
0.14.0 16 Jan 2025 H1 U1 — Yes Details →
0.13.0 20 Sep 2024 H1 U1 — Yes Details →
0.12.0 26 Apr 2023 H1 U1 — Yes Details →
0.11.0 19 Aug 2022 H1 U1 — Yes Details →
0.10.0 13 May 2022 H1 U1 — Yes Details →
0.9.0 09 Dec 2021 H1 U1 — Yes Details →
0.8.0 03 Nov 2021 H1 U1 — Yes Details →
0.8.0-beta.1 09 Jan 2020 none — — Details →
0.8.0-beta 09 Jan 2020 none — — Details →
0.7.1 07 Jan 2020 none — — Details →
0.7.0 19 Dec 2019 none — — Details →
0.6.3 19 Aug 2019 none — — Details →
0.6.2 19 Jun 2019 none — — Details →
0.6.1 27 Mar 2019 none — — Details →
0.5.4 10 Apr 2018 none — — Details →
0.5.3 01 Mar 2018 none — — Details →
0.5.2 16 Feb 2018 none — — Details →
0.5.0 27 Nov 2017 none — — Details →
0.4.1 13 Sep 2017 none — — Details →
0.4.0 13 Sep 2017 none — — Details →
0.3.4 29 Aug 2017 none — — Details →
0.3.3 20 Aug 2017 none — — Details →
0.3.2 12 Aug 2017 none — — Details →
0.3.1 05 Aug 2017 none — — Details →
0.3.0 05 Aug 2017 none — — Details →
0.2.0 01 Aug 2017 none — — Details →
0.1.0 26 May 2017 none — — Details →

All 33 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 2

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

03 Vulnerabilities

Recorded vulnerabilities for protobuf

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-54451: Protobuf Package Suffers from Unbounded Recursion Depth in Embedded-Message Decoding 8.2 high 0.16.1 15 Jul 2026
CVE-2026-104635: Uncontrolled Recursion in elixir-protobuf Package JSON Decoding 8.2 high 0.17.1 09 Oct 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: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 protobuf

Is protobuf safe to use?

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

Vulert scores protobuf 91/100, which reads as healthy. 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 protobuf affected?

No. 0.17.1, 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 protobuf have?

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

2 vulnerabilities were recorded for protobuf in the last 12 months, and the oldest entry in this database dates to 15 Jul 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 protobuf 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 protobuf for upcoming vulnerabilities?

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