Update dependency protobuf to v6 [SECURITY]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
protobuf	^3.15.8 → ^6.0.0
protobuf	==3.15.8 → ==6.33.5

GitHub Vulnerability Alerts

CVE-2022-1941

Summary

A message parsing and memory management vulnerability in ProtocolBuffer’s C++ and Python implementations can trigger an out of memory (OOM) failure when processing a specially crafted message, which could lead to a denial of service (DoS) on services using the libraries.

Reporter: ClusterFuzz

Affected versions: All versions of C++ Protobufs (including Python) prior to the versions listed below.

Severity & Impact

As scored by google
Medium 5.7 - CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Asscored byt NIST
High 7.5 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

A small (~500 KB) malicious payload can be constructed which causes the running service to allocate more than 3GB of RAM.

Proof of Concept

For reproduction details, please refer to the unit test that identifies the specific inputs that exercise this parsing weakness.

Mitigation / Patching

Please update to the latest available versions of the following packages:

• protobuf-cpp (3.18.3, 3.19.5, 3.20.2, 3.21.6)
• protobuf-python (3.18.3, 3.19.5, 3.20.2, 4.21.6)

CVE-2025-4565

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 SGROUP tags 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=python environment 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:

• protobuf-python(4.25.8, 5.29.5, 6.31.1)

CVE-2026-0994

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.

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: poetry.lock

Updating dependencies
Resolving dependencies...


The current project's Python requirement (>=3.7,<4.0) is not compatible with some of the required packages Python requirement:
  - protobuf requires Python >=3.9, so it will not be satisfied for Python >=3.7,<3.9
  - protobuf requires Python >=3.9, so it will not be satisfied for Python >=3.7,<3.9
  - protobuf requires Python >=3.9, so it will not be satisfied for Python >=3.7,<3.9
  - protobuf requires Python >=3.9, so it will not be satisfied for Python >=3.7,<3.9
  - protobuf requires Python >=3.9, so it will not be satisfied for Python >=3.7,<3.9
  - protobuf requires Python >=3.9, so it will not be satisfied for Python >=3.7,<3.9
  - protobuf requires Python >=3.9, so it will not be satisfied for Python >=3.7,<3.9
  - protobuf requires Python >=3.9, so it will not be satisfied for Python >=3.7,<3.9
  - protobuf requires Python >=3.9, so it will not be satisfied for Python >=3.7,<3.9
  - protobuf requires Python >=3.9, so it will not be satisfied for Python >=3.7,<3.9
  - protobuf requires Python >=3.9, so it will not be satisfied for Python >=3.7,<3.9
  - protobuf requires Python >=3.9, so it will not be satisfied for Python >=3.7,<3.9
  - protobuf requires Python >=3.9, so it will not be satisfied for Python >=3.7,<3.9

Because no versions of protobuf match >=6.0.0,<6.30.0 || >6.30.0,<6.30.1 || >6.30.1,<6.30.2 || >6.30.2,<6.31.0 || >6.31.0,<6.31.1 || >6.31.1,<6.32.0 || >6.32.0,<6.32.1 || >6.32.1,<6.33.0 || >6.33.0,<6.33.1 || >6.33.1,<6.33.2 || >6.33.2,<6.33.3 || >6.33.3,<6.33.4 || >6.33.4,<6.33.5 || >6.33.5,<7.0.0
 and protobuf (6.30.0) requires Python >=3.9, protobuf is forbidden.
And because protobuf (6.30.1) requires Python >=3.9, protobuf is forbidden.
And because protobuf (6.30.2) requires Python >=3.9
 and protobuf (6.31.0) requires Python >=3.9, protobuf is forbidden.
And because protobuf (6.31.1) requires Python >=3.9
 and protobuf (6.32.0) requires Python >=3.9, protobuf is forbidden.
And because protobuf (6.32.1) requires Python >=3.9
 and protobuf (6.33.0) requires Python >=3.9, protobuf is forbidden.
And because protobuf (6.33.1) requires Python >=3.9
 and protobuf (6.33.2) requires Python >=3.9, protobuf is forbidden.
And because protobuf (6.33.3) requires Python >=3.9
 and protobuf (6.33.4) requires Python >=3.9, protobuf is forbidden.
So, because protobuf (6.33.5) requires Python >=3.9
 and autocsr depends on protobuf (^6.0.0), version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For protobuf, a possible solution would be to set the `python` property to ">=3.9,<4.0"
    For protobuf, a possible solution would be to set the `python` property to ">=3.9,<4.0"
    For protobuf, a possible solution would be to set the `python` property to ">=3.9,<4.0"
    For protobuf, a possible solution would be to set the `python` property to ">=3.9,<4.0"
    For protobuf, a possible solution would be to set the `python` property to ">=3.9,<4.0"
    For protobuf, a possible solution would be to set the `python` property to ">=3.9,<4.0"
    For protobuf, a possible solution would be to set the `python` property to ">=3.9,<4.0"
    For protobuf, a possible solution would be to set the `python` property to ">=3.9,<4.0"
    For protobuf, a possible solution would be to set the `python` property to ">=3.9,<4.0"
    For protobuf, a possible solution would be to set the `python` property to ">=3.9,<4.0"
    For protobuf, a possible solution would be to set the `python` property to ">=3.9,<4.0"
    For protobuf, a possible solution would be to set the `python` property to ">=3.9,<4.0"
    For protobuf, a possible solution would be to set the `python` property to ">=3.9,<4.0"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers