protobuf.js: Denial of service from crafted field names in generated code
Published 12 May 2026 · Updated 10 Sept 2026
Is your project on an affected protobufjs?
Look after several JavaScript apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <7.5.6
- Fixed in
- 7.5.6
npm install protobufjs@7.5.6- Affected
- >=8.0.0 <8.0.2
- Fixed in
- 8.0.2
npm install protobufjs@8.0.2Details
Summary
protobufjs generated JavaScript property accessors from schema-controlled field and oneof names. Certain control characters in field names were not escaped before being embedded into generated function bodies. A crafted schema or JSON descriptor could therefore cause generated encode, decode, verify, or conversion functions to fail during compilation.
Impact
An attacker who can provide or influence a protobuf schema or JSON descriptor may be able to make affected message types unusable by causing protobufjs runtime code generation to throw a syntax error.
This is a denial of service issue for applications that load untrusted schemas or descriptors. Applications that only use trusted, application-defined schemas are not directly affected by this issue.
The issue is not known to allow code execution by itself.
Preconditions
- The application must allow an attacker to control or influence a protobuf schema or JSON descriptor.
- The crafted input must define a field name containing control characters that reach generated JavaScript property access.
- The application must perform an operation that triggers protobufjs code generation for the affected type, such as encode, decode, verify,
fromObject, ortoObject.
Workarounds
Do not load protobuf schemas or JSON descriptors from untrusted sources with affected versions. If untrusted schemas must be accepted, validate field names before loading them and reject names containing control characters.
Is GHSA-2pr8-phx7-x9h3 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected protobufjs, and gives you the command that fixes it.
More advisories for protobufjs
- MediumCVE-2026-59876protobufjs: Text Format string map parsing can mutate returned map object prototype · 20 Jul 2026
- MediumCVE-2026-59877protobufjs: Denial of Service via infinite loop in .proto option parsing · 20 Jul 2026
- MediumCVE-2026-54270protobufjs: Memory amplification from preserved unknown fields in binary decode · 15 Jun 2026
- HighCVE-2026-48712protobufjs: Denial of service through unbounded Any expansion during JSON conversion · 15 Jun 2026
- MediumCVE-2026-54269protobufjs : Schema-derived names can shadow runtime-significant properties · 15 Jun 2026
- MediumCVE-2026-45740protobufjs: Denial of Service via unbounded recursive JSON descriptor expansion · 19 May 2026
References
- Linkgithub.com/protobufjs/protobuf.js/security/advisories/GHSA-2pr8-phx7-x9h3
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-44294
- Packagegithub.com/protobufjs/protobuf.js
- Linkgithub.com/protobufjs/protobuf.js/releases/tag/protobufjs-v7.5.6
- Linkgithub.com/protobufjs/protobuf.js/releases/tag/protobufjs-v8.0.2
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.