chore(deps): update dependency protobuf to v5.29.6 [security]#14346
chore(deps): update dependency protobuf to v5.29.6 [security]#14346renovate-bot wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
Code Review
This pull request updates the protobuf dependency to version 5.29.6 across several requirements.txt files. However, this upgrade introduces dependency resolution conflicts in multiple modules (such as hello-datastore, hello-firestore, and upper-firestore) where google-api-core is pinned to version 2.17.1, which strictly requires protobuf < 5.0.0.dev. To resolve this, you should either upgrade google-api-core to a version supporting protobuf v5 or keep protobuf on a compatible 4.x version.
| google-cloud-datastore==2.20.2 | ||
| google-api-core==2.17.1 | ||
| protobuf==4.25.8 | ||
| protobuf==5.29.6 |
There was a problem hiding this comment.
Upgrading protobuf to 5.29.6 (v5) will cause a dependency resolution conflict because google-api-core==2.17.1 strictly requires protobuf < 5.0.0.dev.
To resolve this conflict, please either:
- Upgrade
google-api-coreto a version that supports protobuf v5 (e.g.,google-api-core==2.23.0or>= 2.19.0). - Keep
protobufon a compatible 4.x version (such as4.25.8or4.25.9if available) that addresses the security vulnerabilities.
| google-events==0.14.0 | ||
| google-api-core==2.17.1 | ||
| protobuf==4.25.6 | ||
| protobuf==5.29.6 |
There was a problem hiding this comment.
Upgrading protobuf to 5.29.6 (v5) will cause a dependency resolution conflict because google-api-core==2.17.1 strictly requires protobuf < 5.0.0.dev.
To resolve this conflict, please either:
- Upgrade
google-api-coreto a version that supports protobuf v5 (e.g.,google-api-core==2.23.0or>= 2.19.0). - Keep
protobufon a compatible 4.x version (such as4.25.8or4.25.9if available) that addresses the security vulnerabilities.
| google-events==0.14.0 | ||
| google-api-core==2.17.1 | ||
| protobuf==4.25.6 | ||
| protobuf==5.29.6 |
There was a problem hiding this comment.
Upgrading protobuf to 5.29.6 (v5) will cause a dependency resolution conflict because google-api-core==2.17.1 strictly requires protobuf < 5.0.0.dev.
To resolve this conflict, please either:
- Upgrade
google-api-coreto a version that supports protobuf v5 (e.g.,google-api-core==2.23.0or>= 2.19.0). - Keep
protobufon a compatible 4.x version (such as4.25.8or4.25.9if available) that addresses the security vulnerabilities.
This PR contains the following updates:
==5.29.4→==5.29.6==5.29.5→==5.29.6==4.25.6→==5.29.6==4.25.8→==5.29.6protobuf-python has a potential Denial of Service issue
CVE-2025-4565 / GHSA-8qvm-5x2c-j2w7
More information
Details
Summary
Any project that uses Protobuf pure-Python backend to parse untrusted Protocol Buffers data containing an arbitrary number of recursive groups, recursive messages or a series of
SGROUPtags can be corrupted by exceeding the Python recursion limit.Reporter: Alexis Challande, Trail of Bits Ecosystem Security Team
ecosystem@trailofbits.com
Affected versions: This issue only affects the pure-Python implementation of protobuf-python backend. This is the implementation when
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=pythonenvironment variable is set or the default when protobuf is used from Bazel or pure-Python PyPi wheels. CPython PyPi wheels do not use pure-Python by default.This is a Python variant of a previous issue affecting protobuf-java.
Severity
This is a potential Denial of Service. Parsing nested protobuf data creates unbounded recursions that can be abused by an attacker.
Proof of Concept
For reproduction details, please refer to the unit tests decoder_test.py and message_test
Remediation and Mitigation
A mitigation is available now. Please update to the latest available versions of the following packages:
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
protobuf affected by a JSON recursion depth bypass
CVE-2026-0994 / GHSA-7gcm-g887-7qv7
More information
Details
A denial-of-service (DoS) vulnerability exists in google.protobuf.json_format.ParseDict() in Python, where the max_recursion_depth limit can be bypassed when parsing nested google.protobuf.Any messages.
Due to missing recursion depth accounting inside the internal Any-handling logic, an attacker can supply deeply nested Any structures that bypass the intended recursion limit, eventually exhausting Python’s recursion stack and causing a RecursionError.
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Never, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.