Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-54269: protobufjs compiles protobuf definitions into JavaScript (JS) functions

32
Routine
MEDIUM 5.3REMOTEUPGRADEUPGRADE

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

protobufjs compiles protobuf definitions into JavaScript (JS) functions. Prior to 8.6.0 and 7.6.3, protobufjs accepted certain schema-derived names that could collide with properties used by protobufjs runtime helpers. The known affected names are fields named hasOwnProperty, field or oneof names such as $type when loaded through protobufjs JSON/reflection descriptors, and service methods whose generated helper name is rpcCall. When affected mess

Why this priority

  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score5.3 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.4% (top 66%)
CISA exploited listNo
WeaknessCWE-674, CWE-754
Published2026-06-22
Last modified2026-10-25
Publisher (CNA): GitHub, Inc. · Vendor: protobufjs project

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

protobufjs project protobufjs UPGRADE
Affected: < 7.6.3 · >= 8.0.0 and < 8.6.0
Fixed in: 7.6.3, 8.6.0
Safe to downgrade to: a release before 8.0.0
1. Check installed version
npm ls protobufjs
2. UPGRADE to 7.6.3
npm install protobufjs@">=7.6.3"
3. If no update is available yet, DOWNGRADE to a release before 8.0.0
npm view protobufjs versions npm install protobufjs@"<8.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.
protobufjs project protobufjs-cli UPGRADE
Affected: < 1.3.3 · >= 2.0.0 and < 2.5.1
Fixed in: 1.3.3, 2.5.1
Safe to downgrade to: a release before 2.0.0
1. Check installed version
npm ls protobufjs-cli
2. UPGRADE to 1.3.3
npm install protobufjs-cli@">=1.3.3"
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-54269?

protobufjs: upgrade to 7.6.3, 8.6.0; protobufjs-cli: upgrade to 1.3.3, 2.5.1. Exact commands for each OS are on this page.

Is CVE-2026-54269 being exploited?

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

CVE-2026-54269 affects protobufjs, protobufjs-cli. Severity is medium (CVSS 5.3). protobufjs compiles protobuf definitions into JavaScript (JS) functions. Prior to 8.6.0 and 7.6.3, protobufjs accepted certain schema-derived names that could collide with properties used by protobufjs runtime helpers. The known affected na

How urgent is CVE-2026-54269?

Priority 32/100. Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.