CVE-2026-44295: protobuf.js: Code injection in pbjs static output from crafted schema names
Summary pbjs static code generation could emit unsafe JavaScript identifiers derived from schema-controlled names. When generating static JavaScript from a crafted schema or JSON descriptor, certain namespace, enum, service, or derived full names could be written into the generated output without sufficient sanitization.
Published May 12, 2026 · Updated May 14, 2026
Affected packages
protobufjs-cli
- Ecosystem
- npm
- Affected
- <= 1.2.0
- Fixed in
- 1.2.1
- Check
npm ls protobufjs-cli
protobufjs-cli
- Ecosystem
- npm
- Affected
- >= 2.0.0, <= 2.0.1
- Fixed in
- 2.0.2
- Check
npm ls protobufjs-cli
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
pbjs static code generation could emit unsafe JavaScript identifiers derived from schema-controlled names. When generating static JavaScript from a crafted schema or JSON descriptor, certain namespace, enum, service, or derived full names could be written into the generated output without sufficient sanitization.
Impact
An attacker who can provide or influence schemas passed to pbjs may be able to cause generated JavaScript output to contain attacker-controlled code. The injected code would run if the generated file is later executed or imported by the application or build process.
This affects the protobufjs CLI static code generation path. Applications that only use trusted schemas, or that do not execute generated output from untrusted schemas, are not directly affected.
Preconditions
- The application or build process must run
pbjsstatic code generation on a schema or JSON descriptor influenced by an attacker. - The attacker-controlled input must contain crafted schema names that reach generated JavaScript output.
- The generated JavaScript file must subsequently be executed, imported, or otherwise evaluated.
Workarounds
Do not run affected versions of pbjs static code generation on untrusted schemas or descriptors. If untrusted schemas must be accepted, validate schema names before code generation and run generation in an isolated environment.
Credited to VladimirEliTokarev, dcodeIO.
References
- https://github.com/protobufjs/protobuf.js/security/advisories/GHSA-6r35-46g8-jcw9
- https://github.com/protobufjs/protobuf.js/releases/tag/protobufjs-cli-v1.2.1
- https://github.com/protobufjs/protobuf.js/releases/tag/protobufjs-cli-v2.0.2
- https://nvd.nist.gov/vuln/detail/CVE-2026-44295
- https://github.com/advisories/GHSA-6r35-46g8-jcw9
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-54271
protobufjs-cli: Code injection in pbjs static output from crafted JSON descriptor names
high8.2Jun 15, 2026CVE-2026-42290
protobuf.js is Vulnerable to OS Command Injection in the CLI
high7.8May 12, 2026
