CVE-2026-44290: protobuf.js: Process-wide denial of service through unsafe option paths
Summary protobufjs allowed certain schema option paths to traverse through inherited object properties while applying options. A crafted protobuf schema or JSON descriptor could cause option handling to write to properties on global JavaScript constructors, corrupting process-wide built-in functionality.
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 allowed certain schema option paths to traverse through inherited object properties while applying options. A crafted protobuf schema or JSON descriptor could cause option handling to write to properties on global JavaScript constructors, corrupting process-wide built-in functionality.
Impact
An attacker who can provide or influence protobuf schemas or JSON descriptors may be able to corrupt built-in process state in a way that causes subsequent application code or protobufjs code to fail. This can result in a persistent denial of service for the lifetime of the affected process.
This issue affects applications that parse or load protobuf schemas or descriptors from untrusted sources. Applications that use bundled, generated, or otherwise trusted schemas to decode untrusted protobuf message payloads are not directly affected.
The issue is not known to allow code execution by itself.
Preconditions
- The application must allow an attacker to control or influence a protobuf schema or JSON descriptor.
- The application must parse or load that schema through protobufjs reflection APIs such as
parse,Root.load,Root.loadSync, orRoot.fromJSON. - The crafted input must contain option paths that reach unsafe inherited properties during option processing.
Workarounds
Do not parse or load protobuf schemas or JSON descriptors from untrusted sources with affected versions. If untrusted schemas must be accepted, validate or reject option names containing unsafe property path components before loading them, and run schema processing in an isolated process.
Credited to AKiileX, VladimirEliTokarev, dcodeIO.
References
- https://github.com/protobufjs/protobuf.js/security/advisories/GHSA-jvwf-75h9-cwgg
- 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-44290
- https://github.com/advisories/GHSA-jvwf-75h9-cwgg
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
