protobufjs-cli
Affected
- introduced
0, fixed1.3.2(semver)
Fixed versions
1.3.2
Fix
- Fixed version
1.3.2npm install [email protected]
Advisory
Also known as: 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.
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
pbjs static code generation on a pre-parsed JSON descriptor influenced by an attacker.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.
High Basis: The source's own band: HIGH
0, fixed 1.3.2 (semver)1.3.2
1.3.2npm install [email protected]2.0.0, fixed 2.5.0 (semver)2.5.0
2.5.0npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0