CVE-2026-54271: protobufjs-cli: Code injection in pbjs static output from crafted JSON descriptor names
Summary A previous fix for unsafe name handling in pbjs static / static-module code generation was incomplete. Affected versions of protobufjs-cli could still emit unsafe JavaScript references when generating static output from crafted JSON descriptor input. The common case of parsing schemas from .proto files is not affected. This is a bypass of GHSA-6r35-46g8-jcw9 / CVE-2026-44295.
Published Jun 15, 2026 · Updated Jul 15, 2026
Affected packages
protobufjs-cli
- Ecosystem
- npm
- Affected
- <= 1.3.1
- Fixed in
- 1.3.2
- Check
npm ls protobufjs-cli
protobufjs-cli
- Ecosystem
- npm
- Affected
- >= 2.0.0, <= 2.4.2
- Fixed in
- 2.5.0
- Check
npm ls protobufjs-cli
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A previous fix for unsafe name handling in pbjs static / static-module code generation was incomplete. Affected versions of protobufjs-cli could still emit unsafe JavaScript references when generating static output from crafted JSON descriptor input. The common case of parsing schemas from .proto files is not affected.
This is a bypass of GHSA-6r35-46g8-jcw9 / CVE-2026-44295.
Impact
An attacker who can provide or influence pre-parsed JSON descriptors passed to pbjs static code generation may be able to cause generated JavaScript output to contain attacker-controlled code.
The injected code may execute if the generated file is later executed or imported and an affected generated API path is invoked.
Preconditions
- The application or build process must run
pbjsstatic code generation on a pre-parsed JSON descriptor influenced by an attacker. - The generated JavaScript file must subsequently be executed or imported.
- An affected generated API path must be invoked.
Workarounds
Do not run affected versions of pbjs static or static-module generation on untrusted JSON descriptors. If untrusted JSON descriptors must be accepted, validate descriptor-derived names before code generation and reject names that could not have been produced by parsing a valid .proto file. Running code generation in an isolated environment can reduce impact.
Credited to JacobBrackett, dcodeIO.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-54269
protobufjs : Schema-derived names can shadow runtime-significant properties
medium5.3Jun 15, 2026CVE-2026-42290
protobuf.js is Vulnerable to OS Command Injection in the CLI
high7.8May 12, 2026CVE-2026-44295
protobuf.js: Code injection in pbjs static output from crafted schema names
high8.7May 12, 2026
