CVE-2026-59876: protobufjs: Text Format string map parsing can mutate returned map object prototype
Summary The protobuf.js text format extension parsed string-keyed map entries using ordinary property assignment. A text-format map entry with key proto could therefore change the prototype of the returned map object instead of creating an own map entry. This affected the optional Text Format extension. Other protobufjs input paths, including binary decode, fromObject, and ProtoJSON conversion, are not affected.
Published Jul 20, 2026
Affected packages
protobufjs
- Ecosystem
- npm
- Affected
- >= 8.2.0, <= 8.6.4
- Fixed in
- 8.6.5
- Check
npm ls protobufjs
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The protobuf.js text format extension parsed string-keyed map entries using ordinary property assignment. A text-format map entry with key __proto__ could therefore change the prototype of the returned map object instead of creating an own map entry.
This affected the optional Text Format extension. Other protobufjs input paths, including binary decode, fromObject, and ProtoJSON conversion, are not affected.
Impact
An attacker who can provide protobuf text-format input parsed by an application using protobufjs/ext/textformat may be able to create message objects whose string-keyed map fields have attacker-controlled prototypes.
This is per-object prototype mutation, not global Object.prototype pollution. Impact depends on downstream application logic treating inherited properties as meaningful, for example by using in, truthiness checks, or direct property access on parsed map objects instead of own-property checks.
Applications that do not parse untrusted Text Format input, or that do not use inherited properties from parsed map objects in security-relevant logic, are not directly affected.
Preconditions
- The application must parse attacker-controlled protobuf Text Format input with
protobufjs/ext/textformat. - The target schema must contain a string-keyed map field.
- The crafted input must provide a map entry with key
__proto__. - Downstream application logic must treat inherited properties on the returned map object as meaningful for impact beyond malformed output.
Workarounds
Upgrade to protobufjs 8.6.5 or newer.
If immediate upgrade is not possible, do not parse untrusted protobuf Text Format input with affected versions. Applications can also reject string map keys named __proto__ before or during Text Format parsing, and should use own-property checks such as Object.hasOwnProperty.call(map, key) when consuming parsed map objects.
Credited to Faze-up.
References
- https://github.com/protobufjs/protobuf.js/security/advisories/GHSA-jfj6-75fj-8934
- https://nvd.nist.gov/vuln/detail/CVE-2026-59876
- https://github.com/protobufjs/protobuf.js/pull/2335
- https://github.com/protobufjs/protobuf.js/commit/9f97fe413072d3beb52c74e62d88ea8adc9444d8
- https://github.com/protobufjs/protobuf.js/releases/tag/protobufjs-v8.6.5
- https://github.com/advisories/GHSA-jfj6-75fj-8934
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-59877
protobufjs: Denial of Service via infinite loop in .proto option parsing
medium5.3Jul 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
