CVE-2026-44295

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.

Preconditions

• The application or build process must run pbjs static 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.

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.

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

CVE-2026-44295 has a CVSS score of 8.7 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.2.1, 2.0.2); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-44295? CVE-2026-44295 is a high-severity code injection vulnerability in protobufjs-cli (npm), affecting versions <= 1.2.0. It is fixed in 1.2.1, 2.0.2. Untrusted input is evaluated as executable code within the application's runtime environment.
2. How severe is CVE-2026-44295? CVE-2026-44295 has a CVSS score of 8.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of protobufjs-cli are affected by CVE-2026-44295? protobufjs-cli (npm) versions <= 1.2.0 is affected.
4. Is there a fix for CVE-2026-44295? Yes. CVE-2026-44295 is fixed in 1.2.1, 2.0.2. Upgrade to this version or later.
5. Is CVE-2026-44295 exploitable, and should I be worried? Whether CVE-2026-44295 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-44295 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-44295?
   • Upgrade protobufjs-cli to 1.2.1 or later
   • Upgrade protobufjs-cli to 2.0.2 or later