CVE-2026-44295: protobufjs-cli: Code injection in pbjs static output from crafted schema names

Published May 12, 2026
·
Updated

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 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.

Other sources

protobufjs-cli is the command line add-on for protobuf.js. Prior to 1.2.1 and 2.0.2, 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. This vulnerability is fixed in 1.2.1 and 2.0.2.

MITRE

Affected Software

4 affected componentsFixes available
npm/protobufjs-cli>=2.0.0<=2.0.1
2.0.2
npm/protobufjs-cli<=1.2.0
1.2.1
Protobufjs Project Protobufjs-cli Node.js<1.2.1
Protobufjs Project Protobufjs-cli Node.js>=2.0.0<2.0.2

Event History

May 12, 2026
Advisory Published
via GitHub·03:06 PM
Data Sourced
via GitHub·03:06 PM
DescriptionSeverityWeaknessAffected Software
May 13, 2026
CVE Published
via MITRE·02:50 PM
Data Sourced
via MITRE·02:50 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 PM
Affected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-44295?

CVE-2026-44295 is considered a high severity vulnerability due to the potential for emitting unsafe JavaScript identifiers.

2

What software versions are affected by CVE-2026-44295?

CVE-2026-44295 affects protobufjs-cli versions prior to 2.0.2 and 1.2.0 and below.

3

How do I fix CVE-2026-44295?

To address CVE-2026-44295, update protobufjs-cli to version 2.0.2 or 1.2.1.

4

What kind of vulnerability is CVE-2026-44295?

CVE-2026-44295 is a code generation vulnerability that allows for the generation of unsafe JavaScript identifiers from schema-controlled names.

5

What could be the impact of CVE-2026-44295 on my application?

The impact of CVE-2026-44295 could lead to security issues, such as potential injection attacks resulting from unsafe JavaScript output.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203