CVE-2026-44291: protobuf.js: Code generation gadget after prototype pollution
Summary protobufjs used plain objects with inherited prototypes for internal type lookup tables used by generated encode and decode functions. If Object.prototype had already been polluted, those lookup tables could resolve attacker-controlled inherited properties as valid protobuf type information. This could cause attacker-controlled strings to be emitted into generated JavaScript code.
Published May 12, 2026 · Updated May 14, 2026
Affected packages
protobufjs
- Ecosystem
- npm
- Affected
- <= 7.5.5
- Fixed in
- 7.5.6
- Check
npm ls protobufjs
protobufjs
- Ecosystem
- npm
- Affected
- >= 8.0.0, <= 8.0.1
- Fixed in
- 8.0.2
- Check
npm ls protobufjs
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
protobufjs used plain objects with inherited prototypes for internal type lookup tables used by generated encode and decode functions. If Object.prototype had already been polluted, those lookup tables could resolve attacker-controlled inherited properties as valid protobuf type information.
This could cause attacker-controlled strings to be emitted into generated JavaScript code.
Impact
An attacker who can first trigger a prototype pollution vulnerability may be able to influence generated protobufjs encode or decode functions in a way that can lead to arbitrary JavaScript execution.
This issue requires a separate prototype pollution primitive before protobufjs is invoked.
Applications without a reachable prototype pollution primitive are not directly exploitable through this issue alone.
Preconditions
- The application or one of its dependencies must allow an attacker to pollute
Object.prototype. - The polluted property must affect protobufjs internal type lookup behavior.
- The application must use protobufjs functionality that generates encode or decode code for affected types.
- The generated code path must be reached after the prototype pollution has occurred.
Workarounds
Avoid running affected versions in applications where attacker-controlled input can pollute Object.prototype. If immediate upgrade is not possible, remove or mitigate reachable prototype pollution primitives and isolate schema/message processing from untrusted application state.
Credited to VladimirEliTokarev, dcodeIO.
References
- https://github.com/protobufjs/protobuf.js/security/advisories/GHSA-75px-5xx7-5xc7
- https://github.com/protobufjs/protobuf.js/releases/tag/protobufjs-v7.5.6
- https://github.com/protobufjs/protobuf.js/releases/tag/protobufjs-v8.0.2
- https://nvd.nist.gov/vuln/detail/CVE-2026-44291
- https://github.com/advisories/GHSA-75px-5xx7-5xc7
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-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, 2026
