CVE-2026-59877: protobufjs: Denial of Service via infinite loop in .proto option parsing
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).
Published Jul 20, 2026
Affected packages
protobufjs
- Ecosystem
- npm
- Affected
- >= 7.5.0, <= 7.6.4
- Fixed in
- 7.6.5
- Check
npm ls protobufjs
protobufjs
- Ecosystem
- npm
- Affected
- >= 8.0.0, <= 8.6.5
- Fixed in
- 8.6.6
- Check
npm ls protobufjs
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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
.protoschema text influenced by an attacker. - The schema must be parsed through APIs such as
parse,Root.load, orRoot.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.
Credited to bilerden.
References
- https://github.com/protobufjs/protobuf.js/security/advisories/GHSA-j3f2-48v5-ccww
- https://nvd.nist.gov/vuln/detail/CVE-2026-59877
- https://github.com/protobufjs/protobuf.js/pull/2352
- https://github.com/protobufjs/protobuf.js/commit/10fba6d54815ceecca8a06b9a6db490c8f5d2217
- https://github.com/protobufjs/protobuf.js/commit/fa5c73add738ceb471e74da8cc2f3727c3d0a69f
- https://github.com/protobufjs/protobuf.js/releases/tag/protobufjs-v7.6.5
- https://github.com/protobufjs/protobuf.js/releases/tag/protobufjs-v8.6.6
- https://github.com/advisories/GHSA-j3f2-48v5-ccww
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-59876
protobufjs: Text Format string map parsing can mutate returned map object prototype
medium4.8Jul 20, 2026CVE-2026-48712
protobufjs: Denial of service through unbounded Any expansion during JSON conversion
high7.5Jun 15, 2026CVE-2026-54269
protobufjs : Schema-derived names can shadow runtime-significant properties
medium5.3Jun 15, 2026CVE-2026-54270
protobufjs: Memory amplification from preserved unknown fields in binary decode
medium5.3Jun 15, 2026CVE-2026-45740
protobufjs: Denial of Service via unbounded recursive JSON descriptor expansion
medium5.3May 19, 2026CVE-2026-44288
protobufjs has overlong UTF-8 decoding
medium5.3May 12, 2026
