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
The application or build process must run pbjs static 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.
Other sources
protobufjs-cli is the command line add-on for protobuf.js. Prior to 1.3.2 and 2.5.0, 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 CVE-2026-44295. 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. This vulnerability is fixed in 1.3.2 and 2.5.0.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/protobufjs-clito a version that resolves this vulnerability.Fixed in 2.5.0 - Upgrade
Upgrade
npm/protobufjs-clito a version that resolves this vulnerability.Fixed in 1.3.2 - Configuration
Validate descriptor-derived names before code generation and reject names that could not have been produced by parsing a valid .proto file.
pbjs static/static-module code generation descriptor_name_validation = reject names that could not have been produced by parsing a valid .proto file - Compensating control
Do not run pbjs static or static-module generation on untrusted JSON descriptors.
- Compensating control
Run pbjs static or static-module code generation in an isolated environment to reduce impact.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-54271?
The severity of CVE-2026-54271 is rated as high with a score of 8.2.
What type of vulnerability is CVE-2026-54271?
CVE-2026-54271 is a code injection vulnerability affecting protobufjs-cli.
How do I fix CVE-2026-54271?
To fix CVE-2026-54271, update to the latest version of protobufjs-cli where the issue is resolved.
What does CVE-2026-54271 affect?
CVE-2026-54271 affects the protobufjs-cli tool in the Protobufjs project.
What causes CVE-2026-54271?
CVE-2026-54271 is caused by incomplete sanitization of JSON descriptor names, allowing unsafe JavaScript references.