chore(deps): update dependency protobufjs to v8.6.0 [security] - autoclosed#644
Closed
renovate[bot] wants to merge 1 commit into
Closed
chore(deps): update dependency protobufjs to v8.6.0 [security] - autoclosed#644renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
b5183aa to
404150d
Compare
404150d to
ce91842
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
8.0.3→8.6.0protobufjs: Denial of Service via unbounded recursive JSON descriptor expansion
CVE-2026-45740 / GHSA-jggg-4jg4-v7c6
More information
Details
Summary
protobufjs could recurse without a depth limit while expanding nested JSON descriptors through
Root.fromJSON()andNamespace.addJSON().A crafted JSON descriptor with deeply nested namespace definitions could cause the JavaScript call stack to be exhausted during descriptor loading.
Impact
An attacker who can provide JSON descriptors loaded by an application may be able to crash the process or otherwise cause schema loading to fail with a stack overflow.
This affects applications that load JSON descriptors from untrusted sources with affected versions.
Preconditions
nestednamespace objects.Root.fromJSON()/Namespace.addJSON()descriptor expansion path must process the crafted input.Workarounds
Avoid loading untrusted protobuf JSON descriptors with affected versions. If immediate upgrade is not possible, reject excessively nested descriptor structures at an outer validation boundary where feasible, or isolate descriptor loading in a process that can be safely restarted.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
protobufjs: Denial of service through unbounded Any expansion during JSON conversion
CVE-2026-48712 / GHSA-wcpc-wj8m-hjx6
More information
Details
Summary
protobufjs could recurse without a depth limit while converting decoded messages to plain objects or JSON. This affected generated
toObject()conversion and the customgoogle.protobuf.AnyJSON conversion path.A crafted protobuf binary payload containing deeply nested
Anyvalues could cause the JavaScript call stack to be exhausted during conversion to JSON.Impact
An attacker who can provide protobuf binary data decoded by an application may be able to crash the process or otherwise cause message conversion to fail with a stack overflow.
This affects applications that decode untrusted protobuf input containing
google.protobuf.Anyvalues and then convert decoded messages to JSON or plain objects with JSON conversion enabled, for example throughJSON.stringify(message),Message#toJSON(), orType.toObject(message, { json: true }).Applications that only decode and re-encode protobuf binary data without converting decoded messages to JSON are not directly affected by this issue.
Preconditions
google.protobuf.Any, and the referencedtype_urlmust resolve to a message type in the loaded protobuf root.Anyvalues that are expanded during conversion.Workarounds
Avoid converting untrusted protobuf messages containing
google.protobuf.Anyvalues to JSON with affected versions. If immediate upgrade is not possible, reject or limit messages with deeply nestedAnypayloads at an outer protocol boundary where feasible, avoid JSON conversion of untrustedAnyvalues, or isolate message conversion in a process that can be safely restarted.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
protobufjs : Schema-derived names can shadow runtime-significant properties
CVE-2026-54269 / GHSA-f38q-mgvj-vph7
More information
Details
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$typewhen loaded through protobufjs JSON/reflection descriptors, and service methods whose generated helper name isrpcCall.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,$typethrough protobufjs JSON/reflection descriptor input,rpcCall.verify, ortoObjectforhasOwnProperty; reflected message JSON serialization for$type; or protobufjs RPC service invocation forrpcCall.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.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
protobufjs/protobuf.js (protobufjs)
v8.6.0Compare Source
Features
Bug Fixes
v8.5.0Compare Source
Features
Bug Fixes
v8.4.2Compare Source
Bug Fixes
v8.4.1Compare Source
Bug Fixes
v8.4.0Compare Source
Features
v8.3.0Compare Source
Features
v8.2.1Compare Source
Bug Fixes
Performance Improvements
v8.2.0Compare Source
Features
Bug Fixes
Performance Improvements
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.