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

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

protobufjs: upgrade to 7.6.5, 8.6.6. Exact commands for each OS are on this page.

Q: Is CVE-2026-59877 being exploited?

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

CVE-2026-59877 affects protobufjs. Severity is medium (CVSS 5.3). protobufjs compiles protobuf definitions into JavaScript (JS) functions. Prior to 7.6.5 and 8.6.6, protobufjs parsed option names by advancing through schema tokens until reaching an = token without checking for end of input, so a crafted .

Q: How urgent is CVE-2026-59877?

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

Routine

MEDIUM 5.3REMOTEUPGRADE

CVE-2026-59877 is a medium-severity flaw (CVSS 5.3) affecting protobufjs. 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 7.6.5 and 8.6.6, protobufjs parsed option names by advancing through schema tokens until reaching an = token without checking for end of input, so a crafted .proto schema that opens an option declaration and ends prematurely can cause parse, Root.load, or Root.loadSync to loop indefinitely. This issue is fixed in versions 7.6.5 and 8.6.6.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 70%)
CISA exploited list	No
Weakness	CWE-835
Published	2026-07-08
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-07-08 16:16 UTCPublished CVE record published
2026-10-25 17:10 UTCUpdated Record last modified

protobufjs project protobufjs UPGRADE

Affected: < 7.6.5 · >= 8.0.0 and < 8.6.6

Fixed in: 7.6.5, 8.6.6

Safe to downgrade to: a release before 8.0.0

1. Check installed version

npm ls protobufjs

2. UPGRADE to 7.6.5

npm install protobufjs@">=7.6.5"

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.

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

protobufjs: upgrade to 7.6.5, 8.6.6. Exact commands for each OS are on this page.

Is CVE-2026-59877 being exploited?

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

CVE-2026-59877 affects protobufjs. Severity is medium (CVSS 5.3). protobufjs compiles protobuf definitions into JavaScript (JS) functions. Prior to 7.6.5 and 8.6.6, protobufjs parsed option names by advancing through schema tokens until reaching an = token without checking for end of input, so a crafted .

How urgent is CVE-2026-59877?

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

Related CVEs

CVE-2026-59876 MEDIUM 4.8 UPGRADE protobufjs compiles protobuf definitions into JavaScript (JS) functions

References

← Back to latest CVEs