CVE-2026-44294: protobuf.js: Denial of service from crafted field names in generated code
Summary protobufjs generated JavaScript property accessors from schema-controlled field and oneof names. Certain control characters in field names were not escaped before being embedded into generated function bodies. A crafted schema or JSON descriptor could therefore cause generated encode, decode, verify, or conversion functions to fail during compilation.
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 generated JavaScript property accessors from schema-controlled field and oneof names. Certain control characters in field names were not escaped before being embedded into generated function bodies. A crafted schema or JSON descriptor could therefore cause generated encode, decode, verify, or conversion functions to fail during compilation.
Impact
An attacker who can provide or influence a protobuf schema or JSON descriptor may be able to make affected message types unusable by causing protobufjs runtime code generation to throw a syntax error.
This is a denial of service issue for applications that load untrusted schemas or descriptors. Applications that only use trusted, application-defined schemas are not directly affected by this issue.
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 crafted input must define a field name containing control characters that reach generated JavaScript property access.
- The application must perform an operation that triggers protobufjs code generation for the affected type, such as encode, decode, verify,
fromObject, ortoObject.
Workarounds
Do not load protobuf schemas or JSON descriptors from untrusted sources with affected versions. If untrusted schemas must be accepted, validate field names before loading them and reject names containing control characters.
Credited to VladimirEliTokarev, dcodeIO.
References
- https://github.com/protobufjs/protobuf.js/security/advisories/GHSA-2pr8-phx7-x9h3
- 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-44294
- https://github.com/advisories/GHSA-2pr8-phx7-x9h3
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
