VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

protobufjs: vulnerability history, versions and safety

protobufjs is a package in the npm ecosystem. Vulert records 18 vulnerabilities for it across 98 releases, from Oct 2018 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
18 vulnerabilities recorded C2 H6 M10
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
14 in the last 12 months

Most recent disclosure 20 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all protobufjs vulnerabilities

Vulert verdict on protobufjs 8.8.1 i

Updated on 23 Oct 2026

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

Package health score 65/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 8.8.1 — unaffected i
  • Vulnerabilities on record 18 over 7 years · 14 in the last year i
  • Latest disclosure 20 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 2,789 packages i
  • Stars 10,602 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by the npm registry, 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 protobufjs, 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
8.8.1 11 Oct 2026 none BSD-3-Clause — Details →
7.6.6 27 Aug 2026 none BSD-3-Clause — Details →
8.8.0 27 Aug 2026 none BSD-3-Clause — Details →
8.7.2 08 Aug 2026 none BSD-3-Clause — Details →
8.7.1 13 Jul 2026 none BSD-3-Clause — Details →
8.7.0 06 Jul 2026 none BSD-3-Clause — Details →
7.6.5 04 Jul 2026 none BSD-3-Clause — Details →
8.6.6 04 Jul 2026 none BSD-3-Clause — Details →
8.6.5 23 Jun 2026 none BSD-3-Clause — Details →
8.6.4 16 Jun 2026 M1 BSD-3-Clause Yes Details →
7.6.4 12 Jun 2026 M1 BSD-3-Clause Yes Details →
8.6.3 11 Jun 2026 M1 BSD-3-Clause Yes Details →
8.6.2 09 Jun 2026 M1 BSD-3-Clause Yes Details →
7.6.3 09 Jun 2026 M1 BSD-3-Clause Yes Details →
8.6.1 07 Jun 2026 M1 BSD-3-Clause Yes Details →
8.6.0 04 Jun 2026 M1 BSD-3-Clause Yes Details →
7.6.2 30 May 2026 M2 BSD-3-Clause Yes Details →
8.5.0 29 May 2026 M1 BSD-3-Clause Yes Details →
7.6.1 22 May 2026 M2 BSD-3-Clause Yes Details →
8.4.2 22 May 2026 M2 BSD-3-Clause Yes Details →
8.4.1 21 May 2026 M2 BSD-3-Clause Yes Details →
7.6.0 18 May 2026 H1 M2 BSD-3-Clause Yes Details →
8.4.0 18 May 2026 M2 BSD-3-Clause Yes Details →
7.5.9 17 May 2026 H1 M2 BSD-3-Clause Yes Details →
8.3.0 13 May 2026 M2 BSD-3-Clause Yes Details →
8.2.1 13 May 2026 M2 BSD-3-Clause Yes Details →
7.5.8 12 May 2026 H1 M2 BSD-3-Clause Yes Details →
8.2.0 09 May 2026 M2 BSD-3-Clause Yes Details →
7.5.7 09 May 2026 H1 M3 BSD-3-Clause Yes Details →
6.11.6 03 May 2026 H5 M5 BSD-3-Clause Yes Details →
7.5.6 28 Apr 2026 H1 M3 BSD-3-Clause Yes Details →
8.0.3 27 Apr 2026 none BSD-3-Clause — Details →
8.0.2 27 Apr 2026 none BSD-3-Clause — Details →
7.5.5 15 Apr 2026 H5 M6 BSD-3-Clause Yes Details →
6.11.5 14 Apr 2026 H5 M5 BSD-3-Clause Yes Details →
8.0.1 04 Apr 2026 none BSD-3-Clause — Details →
8.0.0 16 Dec 2025 C1 BSD-3-Clause Yes Details →
7.5.4 15 Aug 2025 H5 M6 BSD-3-Clause Yes Details →
7.5.3 28 May 2025 H5 M6 BSD-3-Clause Yes Details →
8.1.6-experimental 27 May 2025 none BSD-3-Clause — Details →
8.1.5-experimental 27 May 2025 none BSD-3-Clause — Details →
7.5.2 14 May 2025 H5 M6 BSD-3-Clause Yes Details →
8.1.4-experimental 13 May 2025 none BSD-3-Clause — Details →
8.1.3-experimental 12 May 2025 none BSD-3-Clause — Details →
7.5.1 08 May 2025 H5 M6 BSD-3-Clause Yes Details →
8.1.2-experimental 08 May 2025 none BSD-3-Clause — Details →
8.1.1-experimental 07 May 2025 none BSD-3-Clause — Details →
8.1.0-experimental 07 May 2025 none BSD-3-Clause — Details →
7.5.0 15 Apr 2025 H5 M6 BSD-3-Clause Yes Details →
8.0.4-experimental 27 Mar 2025 none BSD-3-Clause — Details →
8.0.3-experimental 25 Mar 2025 none BSD-3-Clause — Details →
8.0.1-experimental 24 Mar 2025 C1 BSD-3-Clause Yes Details →
8.0.0-experimental 21 Mar 2025 none BSD-3-Clause — Details →
7.4.0 22 Aug 2024 H5 M5 BSD-3-Clause Yes Details →
7.3.3 21 Aug 2024 H5 M5 BSD-3-Clause Yes Details →
7.3.2 12 Jun 2024 H5 M5 BSD-3-Clause Yes Details →
7.3.1 11 Jun 2024 H5 M5 BSD-3-Clause Yes Details →
7.3.0 10 May 2024 H5 M5 BSD-3-Clause Yes Details →
7.2.6 16 Jan 2024 H5 M5 BSD-3-Clause Yes Details →
7.2.5 22 Aug 2023 H5 M5 BSD-3-Clause Yes Details →
6.11.4 11 Aug 2023 H5 M5 BSD-3-Clause Yes Details →
7.2.4 27 Jun 2023 C1 H5 M5 BSD-3-Clause Yes Details →
7.2.3 27 Mar 2023 C1 H5 M5 BSD-3-Clause Yes Details →
7.2.2 07 Feb 2023 C1 H5 M5 BSD-3-Clause Yes Details →
7.2.1 02 Feb 2023 C1 H5 M5 BSD-3-Clause Yes Details →
7.2.0 24 Jan 2023 C1 H5 M5 BSD-3-Clause Yes Details →
7.1.2 22 Sep 2022 C1 H5 M5 BSD-3-Clause Yes Details →
7.1.1 10 Sep 2022 C1 H5 M5 BSD-3-Clause Yes Details →
7.1.0 26 Aug 2022 C1 H5 M5 BSD-3-Clause Yes Details →
7.0.0 08 Jul 2022 C1 H5 M5 BSD-3-Clause Yes Details →
6.11.3 20 May 2022 H5 M5 BSD-3-Clause Yes Details →
6.10.3 20 May 2022 H5 M5 BSD-3-Clause Yes Details →
6.11.2 30 Apr 2021 H6 M5 BSD-3-Clause Yes Details →
6.11.1 29 Apr 2021 H6 M5 BSD-3-Clause Yes Details →
6.11.0 29 Apr 2021 H6 M5 BSD-3-Clause Yes Details →
6.11.0-pre 09 Apr 2021 H6 M5 BSD-3-Clause Yes Details →
6.10.2 16 Nov 2020 H5 M5 BSD-3-Clause Yes Details →
6.10.1 16 Jul 2020 H5 M5 BSD-3-Clause Yes Details →
6.10.1-beta.0 16 Jul 2020 H5 M5 BSD-3-Clause Yes Details →
6.10.0 13 Jul 2020 H5 M5 BSD-3-Clause Yes Details →
6.10.0-beta.2 13 Jul 2020 H5 M5 BSD-3-Clause Yes Details →
6.10.0-beta.1 13 Jul 2020 H5 M5 BSD-3-Clause Yes Details →
6.10.0-beta.0 17 Jun 2020 H5 M5 BSD-3-Clause Yes Details →
6.9.0 20 Apr 2020 H5 M5 BSD-3-Clause Yes Details →
6.9.0-beta.0 17 Apr 2020 H5 M5 BSD-3-Clause Yes Details →
6.9.0-pre 17 Apr 2020 H5 M5 BSD-3-Clause Yes Details →
6.8.9 11 Mar 2020 H5 M5 BSD-3-Clause Yes Details →
6.8.8 19 Jul 2018 H5 M5 BSD-3-Clause Yes Details →
6.8.7 18 Jul 2018 H5 M5 BSD-3-Clause Yes Details →
5.0.3 16 May 2018 H5 M5 Apache-2.0 Yes Details →
6.8.6 26 Feb 2018 H5 M5 BSD-3-Clause Yes Details →
6.8.5 19 Feb 2018 H5 M7 BSD-3-Clause Yes Details →
6.8.4 04 Jan 2018 H5 M7 BSD-3-Clause Yes Details →
6.8.3 29 Nov 2017 H5 M7 BSD-3-Clause Yes Details →
6.8.2 29 Nov 2017 H5 M7 BSD-3-Clause Yes Details →
6.8.1 27 Nov 2017 H5 M7 BSD-3-Clause Yes Details →
6.8.0 09 Jun 2017 H5 M7 BSD-3-Clause Yes Details →
6.7.3 08 Apr 2017 H5 M7 BSD-3-Clause Yes Details →
6.7.2 08 Apr 2017 H5 M7 BSD-3-Clause Yes Details →
6.7.1 05 Apr 2017 H5 M7 BSD-3-Clause Yes Details →
6.7.0 02 Apr 2017 H5 M7 — Yes Details →
6.6.5 02 Mar 2017 H5 M7 — Yes Details →
6.6.4 28 Feb 2017 H5 M7 — Yes Details →
6.6.3 30 Jan 2017 H5 M7 — Yes Details →
6.6.2 27 Jan 2017 H5 M7 — Yes Details →
5.0.2 27 Jan 2017 H5 M5 — Yes Details →
6.6.1 24 Jan 2017 H5 M7 — Yes Details →
6.6.0 24 Jan 2017 H5 M7 — Yes Details →
6.5.3 19 Jan 2017 H5 M7 — Yes Details →
6.5.2 19 Jan 2017 H5 M7 — Yes Details →
6.5.1 18 Jan 2017 H5 M7 — Yes Details →
6.5.0 17 Jan 2017 H5 M7 — Yes Details →
6.4.6 11 Jan 2017 H5 M7 — Yes Details →
6.4.5 07 Jan 2017 H5 M7 — Yes Details →
6.4.4 06 Jan 2017 H5 M7 — Yes Details →
6.4.3 06 Jan 2017 H5 M7 — Yes Details →
6.4.1 04 Jan 2017 H5 M7 — Yes Details →
6.4.0 03 Jan 2017 H5 M7 — Yes Details →
6.3.1 27 Dec 2016 H5 M7 — Yes Details →
6.3.0 26 Dec 2016 H5 M7 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2020 1
  • 2022 1
  • 2023 1
  • 2026 14

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

03 Vulnerabilities

Recorded vulnerabilities for protobufjs

The 5 most severe of 18 vulnerabilities recorded for this package

Search all 18 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-36665: protobufjs Prototype Pollution vulnerability 9.8 critical 7.2.5 05 Jul 2023
Critical Arbitrary Code Execution Vulnerability in protobufjs 9.4 critical 8.0.1 16 Apr 2026
CVE-2026-44291: protobuf.js Code Generation Gadget Vulnerability Due to Prototype Pollution 8.1 high 7.5.6 12 May 2026
CVE-2026-44293: protobuf.js Code Injection via Unsafe Default Values in bytes Field 7.7 high 7.5.6 12 May 2026
CVE-2022-25878: Prototype Pollution in protobufjs 7.5 high 6.11.3 28 May 2022

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 protobufjs

Is protobufjs safe to use?

Vulert records 18 vulnerabilities for protobufjs in npm: 2 critical, 6 high, 10 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is protobufjs's Vulert package health score?

Vulert scores protobufjs 65/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).

Is the latest version of protobufjs affected?

No. 8.8.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 protobufjs have?

18 vulnerabilities are recorded for protobufjs in the npm ecosystem: 2 critical, 6 high, 10 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 protobufjs vulnerabilities disclosed?

14 vulnerabilities were recorded for protobufjs in the last 12 months, and the oldest entry in this database dates to 09 Oct 2018. 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 protobufjs 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 protobufjs for upcoming vulnerabilities?

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