VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

protobuf-codegen: vulnerability history, versions and safety

protobuf-codegen is a package in the crates.io ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the crates.io ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all protobuf-codegen vulnerabilities

Vulert verdict on protobuf-codegen 3.7.2 i

Updated on 23 Oct 2026

Good news: 3.7.2, the version you would install today, has no known vulnerabilities.

Package health score 79/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Not enough data

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

  • Current release 3.7.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 65 packages i
  • Last release 19 months ago i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by crates.io, 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-codegen, 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
4.36.2-release 17 Sep 2026 none BSD-3-Clause — Details →
4.36.1-release 31 Aug 2026 none BSD-3-Clause — Details →
4.36.0-rc.2 03 Aug 2026 none BSD-3-Clause — Details →
4.36.0-rc.1 09 Jul 2026 none BSD-3-Clause — Details →
4.35.1-release 11 Jun 2026 none BSD-3-Clause — Details →
4.34.2-release 20 May 2026 none BSD-3-Clause — Details →
4.35.0-release 19 May 2026 none BSD-3-Clause — Details →
4.35.0-rc.2 06 May 2026 none BSD-3-Clause — Details →
4.35.0-rc.1 20 Apr 2026 none BSD-3-Clause — Details →
4.34.1-release 20 Mar 2026 none BSD-3-Clause — Details →
4.33.6-release 18 Mar 2026 none BSD-3-Clause — Details →
4.34.0-release 27 Feb 2026 none BSD-3-Clause — Details →
4.34.0-rc.2 06 Feb 2026 none BSD-3-Clause — Details →
4.33.5-release 29 Jan 2026 none BSD-3-Clause — Details →
4.34.0-rc.1 22 Jan 2026 none BSD-3-Clause — Details →
4.33.4-release 12 Jan 2026 none BSD-3-Clause — Details →
4.33.3-release 09 Jan 2026 none BSD-3-Clause — Details →
4.33.2-release 06 Dec 2025 none BSD-3-Clause — Details →
4.33.1-release 13 Nov 2025 none BSD-3-Clause — Details →
4.33.0-release 15 Oct 2025 none BSD-3-Clause — Details →
4.33.0-rc.2 09 Oct 2025 none BSD-3-Clause — Details →
4.33.0-rc.1 01 Oct 2025 none BSD-3-Clause — Details →
4.32.1-release 11 Sep 2025 none BSD-3-Clause — Details →
4.32.0-release 14 Aug 2025 none BSD-3-Clause — Details →
4.32.0-rc.2 05 Aug 2025 none BSD-3-Clause — Details →
4.32.0-rc.1 22 Jul 2025 none BSD-3-Clause — Details →
4.31.1-release 28 May 2025 none BSD-3-Clause — Details →
4.31.0-release 14 May 2025 none BSD-3-Clause — Details →
4.31.0-rc.2 30 Apr 2025 none BSD-3-Clause — Details →
4.31.0-rc.1 18 Apr 2025 none BSD-3-Clause — Details →
3.7.2 10 Mar 2025 none MIT — Details →
4.31.0-beta1 06 Mar 2025 none BSD-3-Clause — Details →
4.30.0-beta1 18 Dec 2024 none BSD-3-Clause — Details →
3.7.1 15 Oct 2024 none MIT — Details →
3.6.0 30 Sep 2024 none MIT — Details →
3.5.1 19 Aug 2024 none MIT — Details →
3.5.0 26 Jun 2024 none MIT — Details →
3.4.0 26 Feb 2024 none MIT — Details →
3.3.0 02 Oct 2023 none MIT — Details →
3.2.0 26 Sep 2022 none MIT — Details →
2.28.0 26 Sep 2022 none MIT — Details →
3.1.0 22 Jun 2022 none MIT — Details →
3.0.3 31 May 2022 none MIT — Details →
3.0.2 06 May 2022 none MIT — Details →
3.0.1 02 May 2022 none MIT — Details →
3.0.0 02 May 2022 none MIT — Details →
3.0.0-alpha.14 02 May 2022 none MIT — Details →
3.0.0-alpha.13 01 May 2022 none MIT — Details →
3.0.0-alpha.12 30 Apr 2022 none MIT — Details →
3.0.0-alpha.11 29 Apr 2022 none MIT — Details →
3.0.0-alpha.10 11 Apr 2022 none MIT — Details →
3.0.0-alpha.9 04 Apr 2022 none MIT — Details →
3.0.0-alpha.8 21 Feb 2022 none MIT — Details →
3.0.0-alpha.7 20 Feb 2022 none MIT — Details →
3.0.0-alpha.6 08 Feb 2022 none MIT — Details →
2.27.1 05 Feb 2022 none MIT — Details →
2.27.0 03 Feb 2022 none MIT — Details →
3.0.0-alpha.5 02 Feb 2022 none MIT — Details →
3.0.0-alpha.4 02 Feb 2022 none MIT — Details →
3.0.0-alpha.3 01 Feb 2022 none MIT — Details →
2.26.1 01 Feb 2022 none MIT — Details →
2.26.0 31 Jan 2022 none MIT — Details →
3.0.0-alpha.2 01 Nov 2021 none MIT — Details →
3.0.0-alpha.1 24 Oct 2021 none MIT — Details →
2.25.2 24 Oct 2021 none MIT — Details →
2.25.1 21 Aug 2021 none MIT — Details →
2.25.0 08 Aug 2021 none MIT — Details →
2.24.2 08 Aug 2021 none MIT — Details →
2.24.1 11 Jun 2021 none MIT — Details →
2.24.0 11 Jun 2021 none MIT — Details →
2.23.0 26 Apr 2021 none MIT — Details →
2.18.2 28 Mar 2021 none MIT — Details →
2.22.1 18 Mar 2021 none MIT — Details →
2.22.0 06 Feb 2021 none MIT — Details →
2.21.0 06 Feb 2021 none MIT — Details →
2.20.0 06 Jan 2021 none MIT — Details →
2.19.0 05 Jan 2021 none MIT — Details →
2.18.1 22 Nov 2020 none MIT — Details →
2.18.0 04 Oct 2020 none MIT — Details →
2.17.0 12 Aug 2020 none MIT — Details →
2.16.2 06 Jul 2020 none MIT — Details →
2.16.1 06 Jul 2020 none MIT — Details →
2.16.0 06 Jul 2020 none MIT — Details →
2.15.1 28 Jun 2020 none MIT — Details →
2.15.0 21 Jun 2020 none MIT — Details →
2.14.0 11 Apr 2020 none MIT — Details →
2.13.0 09 Apr 2020 none MIT — Details →
2.12.0 26 Mar 2020 none MIT — Details →
2.11.0 23 Mar 2020 none MIT — Details →
2.10.3 23 Mar 2020 none MIT — Details →
2.10.2 01 Mar 2020 none MIT — Details →
2.10.1 12 Jan 2020 none MIT — Details →
2.10.0 01 Jan 2020 none MIT — Details →
2.8.2 31 Dec 2019 none MIT — Details →
2.9.0 30 Sep 2019 none MIT — Details →
2.8.1 06 Sep 2019 none MIT — Details →
2.8.0 23 Jul 2019 none MIT — Details →
2.7.0 01 Jul 2019 none MIT — Details →
2.6.2 03 Jun 2019 none MIT — Details →
2.6.1 26 May 2019 none MIT — Details →
2.6.0 19 May 2019 none — — Details →
2.5.0 15 Apr 2019 none — — Details →
2.4.2 29 Mar 2019 none — — Details →
2.4.0 06 Mar 2019 none — — Details →
2.3.1 05 Mar 2019 none — — Details →
2.3.0 30 Jan 2019 none — — Details →
2.2.5 20 Jan 2019 none — — Details →
2.0.6 13 Jan 2019 none — — Details →
2.1.5 13 Jan 2019 none — — Details →
2.2.4 13 Jan 2019 none — — Details →
2.2.3 13 Jan 2019 none — — Details →
2.2.2 29 Dec 2018 none — — Details →
2.2.1 26 Dec 2018 none — — Details →
2.2.0 17 Nov 2018 none — — Details →
2.1.4 31 Oct 2018 none — — Details →
2.1.3 31 Oct 2018 none — — Details →
2.1.2 28 Oct 2018 none — — Details →
2.1.1 09 Oct 2018 none — — Details →
2.1.0 06 Oct 2018 none — — Details →
2.0.5 21 Sep 2018 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for protobuf-codegen

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 protobuf-codegen

Is protobuf-codegen safe to use?

Vulert has no vulnerabilities on record for protobuf-codegen in crates.io at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is protobuf-codegen's Vulert package health score?

Vulert scores protobuf-codegen 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 protobuf-codegen affected?

No. 3.7.2, 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.

Which version of protobuf-codegen should I use?

3.7.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does protobuf-codegen have?

0 vulnerabilities are recorded for protobuf-codegen in the crates.io ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new protobuf-codegen vulnerabilities disclosed?

0 vulnerabilities were recorded for protobuf-codegen in the last 12 months. 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-codegen 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-codegen for upcoming vulnerabilities?

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