CVE-2026-44295: protobufjs-cli is the command line add-on for protobuf.js

Q: How do I fix CVE-2026-44295?

protobufjs-cli: upgrade to 1.2.1, 2.0.2. Exact commands for each OS are on this page.

Q: Is CVE-2026-44295 being exploited?

CVE-2026-44295 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-44295 affect?

CVE-2026-44295 affects protobufjs-cli. Severity is high (CVSS 8.7). 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

Routine

HIGH 8.7UPGRADE

CVE-2026-44295 is a high-severity flaw (CVSS 8.7) affecting protobufjs-cli. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.7 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.4% (top 66%)
CISA exploited list	No
Weakness	CWE-94
Published	2026-05-13
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: protobufjs project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-13 16:16 UTCPublished CVE record published
2026-06-17 10:50 UTCUpdated Record last modified

protobufjs project protobufjs-cli UPGRADE

Affected: < 1.2.1 · >= 2.0.0 and < 2.0.2

Fixed in: 1.2.1, 2.0.2

Safe to downgrade to: a release before 2.0.0

1. Check installed version

npm ls protobufjs-cli

2. UPGRADE to 1.2.1

npm install protobufjs-cli@">=1.2.1"

3. If no update is available yet, DOWNGRADE to a release before 2.0.0

npm view protobufjs-cli versions npm install protobufjs-cli@"<2.0.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-44295?

protobufjs-cli: upgrade to 1.2.1, 2.0.2. Exact commands for each OS are on this page.

Is CVE-2026-44295 being exploited?

CVE-2026-44295 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-44295 affect?

CVE-2026-44295 affects protobufjs-cli. Severity is high (CVSS 8.7). 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

How urgent is CVE-2026-44295?

Priority 39/100. High severity

Related CVEs

CVE-2026-54271 HIGH 8.2 UPGRADE protobufjs-cli is the command line add-on for protobuf.js
CVE-2026-54269 MEDIUM 5.3 UPGRADE UPGRADE protobufjs compiles protobuf definitions into JavaScript (JS) functions
CVE-2026-42290 HIGH 7.8 UPGRADE protobufjs-cli is the command line add-on for protobuf.js

References

← Back to latest CVEs