protobufjs-cli: Code injection in pbjs static output from crafted JSON descriptor names
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
protobufjs-clinpm | < 1.3.2 | 1.3.2 |
protobufjs-clinpm | >= 2.0.0, < 2.5.0 | 2.5.0 |
Affected products
4- Range: >= 2.0.0, <= 2.4.2
- osv-coords3 versions
< 24.0.1-r4+ 2 more
- (no CPE)range: < 24.0.1-r4
- (no CPE)range: < 24.0.1-r4
- (no CPE)range: < 1.3.2
Patches
Vulnerability mechanics
References
2News mentions
0No linked articles in our index yet.