VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

protobuf: vulnerability history, versions and safety

protobuf is a package in the PyPI ecosystem. Vulert records 9 vulnerabilities for it across 120 releases, from Sep 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
9 vulnerabilities recorded H3 U6
i
2 with no fix published

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

See the unfixed vulnerabilities →
i
4 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 protobuf vulnerabilities

Vulert verdict on protobuf 7.36.2 i

Updated on 23 Oct 2026

Careful: 7.36.2 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 7.36.2 — affected i
  • Vulnerabilities on record 9 over 8 years · 4 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 2 i
  • Depended on by 40,004 packages i
  • Last release 1 month ago i
  • Licence BSD-3-Clause 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 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
7.37.0rc1 15 Oct 2026 H1 U1 BSD-3-Clause No Details →
7.36.2 17 Sep 2026 H1 U1 BSD-3-Clause No Details →
7.36.1 31 Aug 2026 H1 U1 BSD-3-Clause No Details →
7.36.0 20 Aug 2026 H1 U1 BSD-3-Clause No Details →
7.36.0rc2 03 Aug 2026 H1 U1 BSD-3-Clause No Details →
7.36.0rc1 09 Jul 2026 H1 U1 BSD-3-Clause No Details →
7.35.1 11 Jun 2026 H1 U1 BSD-3-Clause No Details →
7.34.2 20 May 2026 H1 U1 BSD-3-Clause No Details →
7.35.0 19 May 2026 H1 U1 BSD-3-Clause No Details →
7.35.0rc2 06 May 2026 H1 U1 BSD-3-Clause No Details →
7.35.0rc1 20 Apr 2026 H1 U1 BSD-3-Clause No Details →
4.25.9 25 Mar 2026 U1 BSD-3-Clause Yes Details →
7.34.1 20 Mar 2026 H1 U1 BSD-3-Clause No Details →
6.33.6 18 Mar 2026 H1 U1 BSD-3-Clause No Details →
7.34.0 27 Feb 2026 H1 U1 BSD-3-Clause No Details →
7.34.0rc2 06 Feb 2026 H1 U1 BSD-3-Clause No Details →
5.29.6 04 Feb 2026 H1 U1 BSD-3-Clause No Details →
6.33.5 29 Jan 2026 H1 U1 BSD-3-Clause No Details →
7.34.0rc1 22 Jan 2026 H1 U1 BSD-3-Clause No Details →
6.33.4 12 Jan 2026 H1 U1 BSD-3-Clause No Details →
6.33.3 09 Jan 2026 H1 U1 BSD-3-Clause No Details →
6.33.2 06 Dec 2025 H1 U1 BSD-3-Clause No Details →
6.33.1 13 Nov 2025 H1 U1 BSD-3-Clause No Details →
6.33.0 15 Oct 2025 H1 U1 BSD-3-Clause No Details →
6.33.0rc2 09 Oct 2025 H1 U1 BSD-3-Clause No Details →
6.33.0rc1 01 Oct 2025 H1 U1 BSD-3-Clause No Details →
6.32.1 11 Sep 2025 H1 U1 BSD-3-Clause No Details →
6.32.0 14 Aug 2025 H1 U1 BSD-3-Clause No Details →
6.32.0rc2 05 Aug 2025 H1 U1 BSD-3-Clause No Details →
6.32.0rc1 22 Jul 2025 H1 U1 BSD-3-Clause No Details →
5.29.5 28 May 2025 H1 U1 BSD-3-Clause No Details →
6.31.1 28 May 2025 H1 U1 BSD-3-Clause No Details →
4.25.8 28 May 2025 H1 U1 BSD-3-Clause No Details →
6.31.0 14 May 2025 H1 U2 BSD-3-Clause No Details →
6.31.0rc2 30 Apr 2025 H1 U2 BSD-3-Clause No Details →
4.25.7 24 Apr 2025 H2 U2 BSD-3-Clause No Details →
6.31.0rc1 18 Apr 2025 H1 U2 BSD-3-Clause No Details →
6.30.2 26 Mar 2025 H1 U2 BSD-3-Clause No Details →
5.29.4 19 Mar 2025 H1 U2 BSD-3-Clause No Details →
6.30.1 13 Mar 2025 H1 U2 BSD-3-Clause No Details →
6.30.0 05 Mar 2025 H1 U2 BSD-3-Clause No Details →
6.30.0rc2 27 Feb 2025 H1 U2 BSD-3-Clause No Details →
6.30.0rc1 04 Feb 2025 H1 U2 BSD-3-Clause No Details →
4.25.6 24 Jan 2025 H2 U2 BSD-3-Clause No Details →
5.29.3 08 Jan 2025 H1 U2 BSD-3-Clause No Details →
5.29.2 18 Dec 2024 H1 U2 BSD-3-Clause No Details →
5.29.1 04 Dec 2024 H1 U2 BSD-3-Clause No Details →
5.29.0 27 Nov 2024 H1 U2 BSD-3-Clause No Details →
5.29.0rc3 18 Nov 2024 H1 U2 BSD-3-Clause No Details →
5.29.0rc2 23 Oct 2024 H1 U2 BSD-3-Clause No Details →
5.28.3 23 Oct 2024 H1 U2 BSD-3-Clause No Details →
5.29.0rc1 30 Sep 2024 H1 U2 BSD-3-Clause No Details →
5.27.5 18 Sep 2024 H1 U2 BSD-3-Clause No Details →
4.25.5 18 Sep 2024 H2 U2 BSD-3-Clause No Details →
5.28.2 18 Sep 2024 H1 U2 BSD-3-Clause No Details →
5.28.1 11 Sep 2024 H1 U2 BSD-3-Clause No Details →
5.28.0 28 Aug 2024 H1 U2 BSD-3-Clause No Details →
5.27.4 27 Aug 2024 H1 U2 BSD-3-Clause No Details →
5.28.0rc3 22 Aug 2024 H1 U2 BSD-3-Clause No Details →
5.28.0rc2 08 Aug 2024 H1 U2 BSD-3-Clause No Details →
5.27.3 31 Jul 2024 H1 U2 BSD-3-Clause No Details →
4.25.4 24 Jul 2024 H2 U2 BSD-3-Clause No Details →
5.28.0rc1 11 Jul 2024 H1 U2 BSD-3-Clause No Details →
5.27.2 25 Jun 2024 H1 U2 BSD-3-Clause No Details →
5.27.1 06 Jun 2024 H1 U2 BSD-3-Clause No Details →
5.27.0 23 May 2024 H1 U2 BSD-3-Clause No Details →
5.27.0rc3 14 May 2024 H1 U2 BSD-3-Clause No Details →
5.27.0rc2 08 May 2024 H1 U2 BSD-3-Clause No Details →
5.27.0rc1 18 Apr 2024 H1 U2 BSD-3-Clause No Details →
5.26.1 27 Mar 2024 H1 U2 BSD-3-Clause No Details →
5.26.0 13 Mar 2024 H1 U2 BSD-3-Clause No Details →
5.26.0rc3 29 Feb 2024 H1 U2 BSD-3-Clause No Details →
4.25.3 15 Feb 2024 H2 U2 BSD-3-Clause No Details →
5.26.0rc2 06 Feb 2024 H1 U2 BSD-3-Clause No Details →
5.26.0rc1 25 Jan 2024 H1 U2 BSD-3-Clause No Details →
4.25.2 10 Jan 2024 H2 U2 BSD-3-Clause No Details →
4.25.1 15 Nov 2023 H2 U2 BSD-3-Clause No Details →
4.25.0 01 Nov 2023 H2 U2 BSD-3-Clause No Details →
4.25.0rc2 18 Oct 2023 H2 U2 BSD-3-Clause No Details →
4.25.0rc1 16 Oct 2023 H2 U2 BSD-3-Clause No Details →
4.24.4 04 Oct 2023 H2 U2 BSD-3-Clause No Details →
4.24.3 07 Sep 2023 H2 U2 BSD-3-Clause No Details →
4.24.2 25 Aug 2023 H2 U2 BSD-3-Clause No Details →
4.24.1 18 Aug 2023 H2 U2 BSD-3-Clause No Details →
4.24.0 08 Aug 2023 H2 U2 BSD-3-Clause No Details →
4.24.0rc3 01 Aug 2023 H2 U2 BSD-3-Clause No Details →
4.24.0rc2 18 Jul 2023 H2 U2 BSD-3-Clause No Details →
4.24.0rc1 11 Jul 2023 H2 U2 BSD-3-Clause No Details →
4.23.4 06 Jul 2023 H2 U2 BSD-3-Clause No Details →
4.23.3 14 Jun 2023 H2 U2 BSD-3-Clause No Details →
4.23.2 26 May 2023 H2 U2 BSD-3-Clause No Details →
4.23.1 17 May 2023 H2 U2 BSD-3-Clause No Details →
4.22.5 10 May 2023 H2 U2 BSD-3-Clause No Details →
4.23.0 08 May 2023 H2 U2 BSD-3-Clause No Details →
4.23.0rc3 05 May 2023 H2 U2 BSD-3-Clause No Details →
4.22.4 04 May 2023 H2 U2 BSD-3-Clause No Details →
4.23.0rc2 28 Apr 2023 H2 U2 BSD-3-Clause No Details →
4.22.3 13 Apr 2023 H2 U2 BSD-3-Clause No Details →
4.22.1 07 Mar 2023 H2 U2 BSD-3-Clause No Details →
4.22.0 16 Feb 2023 H2 U2 BSD-3-Clause No Details →
4.22.0rc3 10 Feb 2023 H2 U2 — No Details →
4.22.0rc2 02 Feb 2023 H2 U2 — No Details →
4.21.12 14 Dec 2022 H2 U2 — No Details →
4.21.11 08 Dec 2022 H2 U2 — No Details →
4.21.10 30 Nov 2022 H2 U2 — No Details →
4.21.9 26 Oct 2022 H2 U2 — No Details →
4.21.8 18 Oct 2022 H2 U2 — No Details →
3.20.3 29 Sep 2022 H2 U2 — No Details →
3.19.6 29 Sep 2022 H2 U2 — No Details →
4.21.7 29 Sep 2022 H2 U2 — No Details →
4.21.6 13 Sep 2022 H2 U2 — No Details →
3.20.2 13 Sep 2022 H2 U2 — No Details →
3.19.5 13 Sep 2022 H2 U2 — No Details →
3.18.3 13 Sep 2022 H2 U2 — No Details →
4.21.5 09 Aug 2022 H2 U3 — No Details →
4.21.4 26 Jul 2022 H2 U3 — No Details →
4.21.3 21 Jul 2022 H2 U3 — No Details →
4.21.2 24 Jun 2022 H2 U3 — No Details →
4.21.1 27 May 2022 H2 U3 — No Details →
4.21.0 26 May 2022 H2 U3 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 2
  • 2022 2
  • 2025 1
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for protobuf

The 5 most severe of 9 vulnerabilities recorded for this package

Search all 9 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2015-5237: Protobuf Heap-Based Buffer Overflow Vulnerability 8.8 high No fix published 25 Sep 2017
CVE-2025-4565: Denial of Service Vulnerability in Protobuf-Python 8.2 high 4.25.8 16 Jun 2025
CVE-2026-0994: Protobuf JSON Recursion Depth Bypass Vulnerability 8.2 high No fix published 23 Jan 2026
CVE-2026-0994: Protobuf JSON Recursion Depth Bypass Vulnerability 8.2 high 5.29.6 07 Jul 2026
CVE-2025-4565: protobuf Vulnerability Leading to Potential Denial of Service 8.2 high 4.25.8 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 protobuf

Is protobuf safe to use?

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

What is protobuf's Vulert package health score?

Vulert scores protobuf 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of protobuf affected?

Yes. 7.36.2, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of protobuf should I use?

7.36.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 have?

9 vulnerabilities are recorded for protobuf in the PyPI ecosystem: 0 critical, 3 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 protobuf vulnerabilities disclosed?

4 vulnerabilities were recorded for protobuf in the last 12 months, and the oldest entry in this database dates to 25 Sep 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 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.