protobufjs
Affected
- introduced
0, fixed7.5.6(semver)
Fixed versions
7.5.6
Fix
- Fixed version
7.5.6npm install [email protected]
Advisory
Also known as: 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. 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
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.
Medium Basis: The source's own band: MODERATE
0, fixed 7.5.6 (semver)7.5.6
7.5.6npm install [email protected]8.0.0, fixed 8.0.2 (semver)8.0.2
8.0.2npm install [email protected]0, fixed 1.1.1 (semver)1.1.1
1.1.1npm install @protobufjs/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0