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

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

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

Q: Is CVE-2026-54271 being exploited?

CVE-2026-54271 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-54271 affect?

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

Routine

HIGH 8.2UPGRADE

CVE-2026-54271 is a high-severity flaw (CVSS 8.2) 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.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 attac

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.2 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 77%)
CISA exploited list	No
Weakness	CWE-94
Published	2026-06-22
Last modified	2026-10-25

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

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

Am I affected?

Timeline

2026-06-22 18:16 UTCPublished CVE record published
2026-10-25 23:10 UTCUpdated Record last modified

protobufjs project protobufjs-cli UPGRADE

Affected: < 1.3.2 · >= 2.0.0 and < 2.5.0

Fixed in: 1.3.2, 2.5.0

Safe to downgrade to: a release before 2.0.0

1. Check installed version

npm ls protobufjs-cli

2. UPGRADE to 1.3.2

npm install protobufjs-cli@">=1.3.2"

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-54271?

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

Is CVE-2026-54271 being exploited?

CVE-2026-54271 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-54271 affect?

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

How urgent is CVE-2026-54271?

Priority 34/100. High severity

Related CVEs

CVE-2026-54269 MEDIUM 5.3 UPGRADE UPGRADE protobufjs compiles protobuf definitions into JavaScript (JS) functions

References

← Back to latest CVEs