CVE-2026-44293: protobufjs: Code injection through bytes field defaults in generated toObject code
Summary
protobufjs generated JavaScript for toObject conversion could include an unsafe expression derived from a schema-controlled bytes field default value. A crafted descriptor with a non-string default value for a bytes field could cause attacker-controlled code to be emitted into the generated conversion function.
Impact
An attacker who can provide or influence a protobuf descriptor may be able to execute arbitrary JavaScript in the context of the process using protobufjs.
This requires the application to load an attacker-controlled schema or descriptor and then convert a message of the affected type with defaults enabled. Applications that only use trusted, application-defined schemas are not directly affected by this issue.
Preconditions
- The application must allow an attacker to control or influence a protobuf JSON descriptor or equivalent reflected schema. - The descriptor must define a bytes field with an attacker-controlled default value. - The application must call toObject with defaults enabled for the affected type.
Workarounds
Do not load protobuf schemas or JSON descriptors from untrusted sources with affected versions. If untrusted schemas must be accepted, validate or restrict field options before loading them and run schema processing in an isolated environment.
Other sources
protobufjs compiles protobuf definitions into JavaScript (JS) functions. Prior to 7.5.6 and 8.0.2, protobufjs generated JavaScript for toObject conversion could include an unsafe expression derived from a schema-controlled bytes field default value. A crafted descriptor with a non-string default value for a bytes field could cause attacker-controlled code to be emitted into the generated conversion function. This vulnerability is fixed in 7.5.6 and 8.0.2.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/protobufjsto a version that resolves this vulnerability.Fixed in 8.0.2 - Upgrade
Upgrade
npm/protobufjsto a version that resolves this vulnerability.Fixed in 7.5.6 - Upgrade
Upgrade
protobufjsto a version that resolves this vulnerability.Fixed in 7.5.6 - Upgrade
Upgrade
protobufjsto a version that resolves this vulnerability.Fixed in 8.0.2 - Compensating control
Do not load protobuf schemas or JSON descriptors from untrusted sources.
- Compensating control
If untrusted schemas must be accepted, validate or restrict field options before loading them and run schema processing in an isolated environment.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-44293?
CVE-2026-44293 is classified as a high severity vulnerability due to its potential to allow attacker-controlled code execution.
How do I fix CVE-2026-44293?
To fix CVE-2026-44293, update protobufjs to version 8.0.2 or 7.5.6, depending on the version you are using.
What is the impact of CVE-2026-44293?
CVE-2026-44293 can lead to remote code execution by allowing unsafe expressions in generated JavaScript.
Which versions of protobufjs are affected by CVE-2026-44293?
CVE-2026-44293 affects protobufjs versions 8.0.0 to 8.0.1 and 7.5.5 and earlier.
Is there a patch available for CVE-2026-44293?
Yes, patches are available in protobufjs version 8.0.2 and 7.5.6 to address CVE-2026-44293.