protobufjs
Affected
- introduced
0, fixed7.6.3(semver)
Fixed versions
7.6.3
Fix
- Fixed version
7.6.3npm install [email protected]
Advisory
Also known as: CVE-2026-54269
protobufjs : Schema-derived names can shadow runtime-significant properties
Summary
protobufjs accepted certain schema-derived names that could collide with properties used by protobufjs runtime helpers. The known affected names are fields named hasOwnProperty, field or oneof names such as $type when loaded through protobufjs JSON/reflection descriptors, and service methods whose generated helper name is rpcCall.
When affected message or service types were used, protobufjs could read schema-controlled data where it expected an own-property helper, reflected type metadata, or the base RPC helper. This could cause deterministic exceptions or recursive calls in affected decode post-checks, verification, object conversion, reflected JSON serialization, or protobufjs RPC helper invocation.
Impact
An attacker who can provide or influence protobuf schemas or protobufjs JSON descriptors may be able to make affected message or service types unusable, resulting in denial of service for the affected processing path.
Applications using only trusted schemas are affected only if those schemas contain one of the problematic names and the application reaches the affected API path.
The issue is not known to allow code execution by itself.
Preconditions
hasOwnProperty,$type through protobufjs JSON/reflection descriptor input,rpcCall.verify, or toObject for hasOwnProperty; reflected message JSON serialization for $type; or protobufjs RPC service invocation for rpcCall.Workarounds
Do not load protobuf schemas or protobufjs JSON descriptors from untrusted sources with affected versions. If untrusted schemas or descriptors must be accepted, validate schema-derived field, oneof, and service method names before loading and reject the problematic names described above.
Applications using trusted schemas can avoid the issue by renaming affected fields or service methods, or by avoiding the affected API path.
Medium Basis: The source's own band: MODERATE
0, fixed 7.6.3 (semver)7.6.3
7.6.3npm install [email protected]2.0.0, fixed 2.5.1 (semver)2.5.1
2.5.1npm install [email protected]0, fixed 1.3.3 (semver)1.3.3
1.3.3npm install [email protected]8.0.0, fixed 8.6.0 (semver)8.6.0
8.6.0npm install [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