CVE-2026-44294: protobufjs: Denial of service from crafted field names in generated code

Published May 12, 2026
·
Updated

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, or toObject.

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.

Other sources

protobufjs compiles protobuf definitions into JavaScript (JS) functions. Prior to 7.5.6 and 8.0.2, 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. This vulnerability is fixed in 7.5.6 and 8.0.2.

MITRE

Affected Software

4 affected componentsFixes available
npm/protobufjs>=8.0.0<=8.0.1
8.0.2
npm/protobufjs<=7.5.5
7.5.6
Protobufjs Project Protobufjs Node.js<7.5.6
Protobufjs Project Protobufjs Node.js>=8.0.0<8.0.2

Event History

May 12, 2026
Advisory Published
via GitHub·03:06 PM
Data Sourced
via GitHub·03:06 PM
DescriptionSeverityWeaknessAffected Software
May 13, 2026
CVE Published
via MITRE·02:44 PM
Data Sourced
via MITRE·02:44 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-44294?

CVE-2026-44294 is classified with a high severity due to potential security implications from improper handling of control characters in generated JavaScript code.

2

How do I fix CVE-2026-44294?

To fix CVE-2026-44294, update protobufjs to version 8.0.2 or 7.5.6, depending on your current version.

3

Which versions of protobufjs are affected by CVE-2026-44294?

CVE-2026-44294 affects protobufjs versions from 8.0.0 to 8.0.1 and all versions up to 7.5.5.

4

What types of issues does CVE-2026-44294 introduce?

CVE-2026-44294 can lead to security risks such as code injection vulnerabilities through improperly handled field names.

5

Where can I find more information about CVE-2026-44294?

More information about CVE-2026-44294 can be found in the advisories and release notes on the official protobufjs GitHub repository.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203