CVE-2026-44288: protobufjs has overlong UTF-8 decoding
Summary protobufjs includes a minimal UTF-8 decoder used in non-Node and fallback decoding paths. The affected decoder accepted overlong UTF-8 byte sequences and decoded them to their canonical characters instead of replacing them. The issue concerns overlong encodings and code points outside the Unicode range.
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
@protobufjs/utf8
- Ecosystem
- npm
- Affected
- <= 1.1.0
- Fixed in
- 1.1.1
- Check
npm ls @protobufjs/utf8
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
protobufjs includes a minimal UTF-8 decoder used in non-Node and fallback decoding paths. The affected decoder accepted overlong UTF-8 byte sequences and decoded them to their canonical characters instead of replacing them.
The issue concerns overlong encodings and code points outside the Unicode range. protobufjs may still accept some non-strict UTF-8 input for compatibility, so applications should not rely on protobufjs as a general-purpose strict UTF-8 validator.
Impact
An attacker who can provide protobuf binary data decoded through the affected UTF-8 path may be able to bypass application-level checks that inspect raw bytes before protobuf string decoding. For example, bytes that do not contain certain ASCII characters could decode to strings containing those characters.
The practical impact depends on downstream application validation and how decoded strings are used. Node.js Buffer-backed decoding paths are not directly affected when they use Node's native UTF-8 decoding.
Preconditions
- The application must decode protobuf binary data influenced by an attacker.
- The affected protobuf string field must be decoded through protobufjs's minimal UTF-8 decoder rather than a native UTF-8 decoder.
- The application must rely on byte-level filtering or validation before protobuf string decoding.
- The decoded string must then be used in a security-sensitive context.
Workarounds
Avoid relying only on byte-level filtering before protobuf string decoding with affected versions. Validate decoded strings at the point where they are used, and prefer runtime paths that use native UTF-8 decoding where necessary.
Credited to Xvush, dcodeIO.
References
- https://github.com/protobufjs/protobuf.js/security/advisories/GHSA-q6x5-8v7m-xcrf
- 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-44288
- https://github.com/advisories/GHSA-q6x5-8v7m-xcrf
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
