Vulnerability Database · Debian · Package report

protobuf: vulnerability history, versions and safety

protobuf is a package in the Debian ecosystem. Vulert records 15 vulnerabilities for it across 59 releases, from Nov -0001 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
15 vulnerabilities recorded U15
i
9 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 16 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on protobuf i

Updated on 22 Oct 2026

Careful: 9 of the 15 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 15 vulnerabilities on record across 2026 years, 1 in the last year.

What to do: Plan around the 9 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 15 over 2026 years · 1 in the last year i
  • Latest disclosure 16 Apr 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 9 i

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 holds for protobuf, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
4.0.0~rc2-1 U9 No Details →
4.0.0~rc1-1 U9 No Details →
3.25.7-1 U1 No Details →
3.25.4-4 U2 No Details →
3.25.4-3 U2 No Details →
3.25.4-2 U2 No Details →
3.25.4-1 U9 No Details →
3.25.3-1 U9 No Details →
3.25.2-1 U9 No Details →
3.25.1-1 U9 No Details →
3.21.12-15 U2 No Details →
3.21.12-14 U2 No Details →
3.21.12-13 U3 No Details →
3.21.12-12 U3 No Details →
3.21.12-11 U9 No Details →
3.21.12-10 U9 No Details →
3.21.12-9 U9 No Details →
3.21.12-8.2 U9 No Details →
3.21.12-8.1 U9 No Details →
3.21.12-8 U9 No Details →
3.21.12-7 U9 No Details →
3.21.12-6 U9 No Details →
3.21.12-5 U9 No Details →
3.21.12-4 U9 No Details →
3.21.12-3 U9 No Details →
3.21.12-2 U9 No Details →
3.21.12-2+exp1 U9 No Details →
3.21.12-1 U9 No Details →
3.21.11-1 U9 No Details →
3.21.10-1 U9 No Details →
3.21.9-5 U9 No Details →
3.21.9-4 U9 No Details →
3.21.9-3 U9 No Details →
3.21.9-2 U9 No Details →
3.21.9-1 U9 No Details →
3.21.8-1 U9 No Details →
3.21.7-1 U9 No Details →
3.21.6-1 U9 No Details →
3.20.2-1 U9 No Details →
3.20.1-1 U9 No Details →
3.20.1~rc1-1 U9 No Details →
3.20.0-1 U9 No Details →
3.20.0~rc2-1 U9 No Details →
3.20.0~rc1-1 U9 No Details →
3.19.4-1 U9 No Details →
3.19.3-1 U9 No Details →
3.19.1-1 U9 No Details →
3.19.0-1 U9 No Details →
3.18.1-1 U9 No Details →
3.18.0-1 U9 No Details →
3.18.0~rc2-1 U9 No Details →
3.18.0~rc1-1 U9 No Details →
3.17.3-2 U9 No Details →
3.17.3-1 U9 No Details →
3.17.2-1 U9 No Details →
3.17.1-1 U9 No Details →
3.14.0-1 U9 No Details →
3.12.4-1 U15 No Details →
3.12.4-1+deb11u1 U9 No Details →

Newest 59 of 59 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 1
  • 2017 2
  • 2022 9
  • 2024 1
  • 2025 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for protobuf

The 5 most severe of 15 vulnerabilities recorded for this package

Search all 15 in the database →

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 →

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.

Questions

About protobuf

Is protobuf safe to use?

Vulert records 15 vulnerabilities for protobuf in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 15 not yet rated. 9 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does protobuf have?

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

1 vulnerability was recorded for protobuf in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. 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.