CVE-2026-59877: protobufjs: Denial of Service via infinite loop in .proto option parsing

Published Jul 8, 2026
·
Updated

Summary

protobufjs parsed option names by advancing through schema tokens until it reached an = token, without checking for end of input. A crafted .proto schema that opens an option declaration but ends prematurely could cause the option parser to loop without ever terminating.

This affects the reflection parsing path (parse, Root.load, Root.loadSync).

Impact

An attacker who can provide or influence .proto schema text parsed by an application may be able to cause the parsing call to never return. Because Node.js is single-threaded, the blocked event loop prevents all other work in the process, resulting in a denial of service that persists until the process is externally terminated.

Applications that only encode or decode protobuf binary data with trusted schemas are not directly affected.

Preconditions

- The application must parse .proto schema text influenced by an attacker. - The schema must be parsed through APIs such as parse, Root.load, or Root.loadSync. - The crafted input must begin an option declaration that ends before its = assignment.

Workarounds

Do not parse .proto schemas from untrusted sources with affected versions. If untrusted schema text must be accepted, isolate parsing in a process or worker that can be safely terminated and bound it with a timeout, so a non-returning parse call cannot deny service to the rest of the application.

Other sources

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.

MITRE

Affected Software

5 affected componentsFixes available
protobufjs<7.6.5, <8.6.6
Protobufjs Project Protobufjs Node.js<7.6.5
Protobufjs Project Protobufjs Node.js>=8.0.0<8.6.6
npm/protobufjs>=8.0.0<=8.6.5
8.6.6
npm/protobufjs>=7.5.0<=7.6.4
7.6.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/protobufjs to a version that resolves this vulnerability.

    Fixed in 8.6.6
  2. Upgrade

    Upgrade npm/protobufjs to a version that resolves this vulnerability.

    Fixed in 7.6.5
  3. Upgrade

    Upgrade protobufjs to a version that resolves this vulnerability.

    Fixed in 7.6.5
  4. Upgrade

    Upgrade protobufjs to a version that resolves this vulnerability.

    Fixed in 8.6.6
  5. Compensating control

    Do not parse .proto schemas from untrusted sources with affected versions; if untrusted schema text must be accepted, isolate parsing in a process or worker that can be safely terminated and bound it with a timeout so a non-returning parse call cannot deny service to the rest of the application.

Event History

Jul 8, 2026
CVE Published
via MITRE·03:28 PM
Data Sourced
via MITRE·03:28 PM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·04:02 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·04:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 20, 2026
Advisory Published
via GitHub·10:03 PM
Data Sourced
via GitHub·10:03 PM
DescriptionSeverityWeaknessAffected Software
Sep 1, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-59877?

The severity of CVE-2026-59877 is medium with a score of 5.3.

2

How do I fix CVE-2026-59877?

To fix CVE-2026-59877, upgrade protobufjs to version 7.6.5 or 8.6.6 or later.

3

What type of vulnerability is CVE-2026-59877?

CVE-2026-59877 is a Denial of Service vulnerability due to an infinite loop during .proto option parsing.

4

What software is affected by CVE-2026-59877?

CVE-2026-59877 affects protobufjs versions prior to 7.6.5 and 8.6.6.

5

What can happen if CVE-2026-59877 is exploited?

If CVE-2026-59877 is exploited, it may lead to a Denial of Service due to the infinite loop in .proto option parsing.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203