Skip to main content
VulnerabilityPublished

CVE-2026-59877: protobufjs protobuf.js · Infinite Loop

Affects protobufjs protobuf.jsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 8.6.6 or 7.6.5 when convenient.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.6.6, 7.6.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade protobuf.js and protobufjs to 8.6.6 or 7.6.5.

Affected software

ProductAffectedFixed in
protobufjsprotobuf.jsAffected
  • >=8.0.0 <8.6.6
Fixed in
  • 8.6.6
protobufjsprotobuf.jsAffected
  • >=7.5.0 <7.6.5
Fixed in
  • 7.6.5
npmprotobufjspkg:npm/protobufjsOther threatsAffected
  • <7.6.5
  • <8.6.6
Fixed in
  • 7.6.5
  • 8.6.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade protobuf.js to version 7.6.5 or later, or 8.6.6 or later, where this issue is fixed. No other mitigation is indicated. Patch status is confirmed fixed in these versions.

Description

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.

References

Community reviews

Loading reviews…