CVE-2025-4565: Unbounded recursion in Python Protobuf

Published Jun 16, 2025
·
Updated

### 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`](https://protobuf.dev/programming-guides/encoding/#groups) tags** can be corrupted by exceeding the Python recursion limit. Reporter: Alexis Challande, Trail of Bits Ecosystem Security Team [ecosystem@trailofbits.com](mailto:ecosystem@trailofbits.com) Affected versions: This issue only affects the [pure-Python implementation](https://github.com/protocolbuffers/protobuf/tree/main/python#implementation-backends) 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](https://github.com/protocolbuffers/protobuf/security/advisories/GHSA-735f-pc8j-v9w8). ### 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](https://github.com/protocolbuffers/protobuf/blob/main/python/google/protobuf/internal/decoder_test.py#L87-L98) and [message_test](https://github.com/protocolbuffers/protobuf/blob/main/python/google/protobuf/internal/message_test.py#L1436-L1478) ### 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)

Affected Software

7 affected componentsFixes available
pip/protobuf>=6.30.0rc1<6.31.1
6.31.1
pip/protobuf>=5.26.0rc1<5.29.5
5.29.5
pip/protobuf<4.25.8
4.25.8
Google protobuf-python<4.25.8
Google protobuf-python>=5.26.0<5.29.5
Google protobuf-python>=6.30.0<6.31.1
IBM Knowledge Catalog Standard Cartridge<=5.0.0, 5.0.1, 5.0.2, 5.0.3, 5.1, 5.1.1, 5,1.2, 5.1.3, 5.2.0, 5.2.1

Event History

Jun 16, 2025
CVE Published
via MITRE·02:50 PM
Data Sourced
via MITRE·02:50 PM
DescriptionWeakness
Data Sourced
via Red Hat·03:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·03:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:15 PM
RemedyAffected Software
Advisory Published
via GitHub·04:02 PM
Data Sourced
via GitHub·04:02 PM
DescriptionWeaknessAffected Software
Mar 25, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-4565?

CVE-2025-4565 has been classified with a high severity rating due to its potential to cause denial of service through resource exhaustion.

2

How do I fix CVE-2025-4565?

To fix CVE-2025-4565, upgrade your protobuf package to version 6.31.1 or newer, 5.29.5 or newer, or 4.25.8 or newer.

3

What software is affected by CVE-2025-4565?

CVE-2025-4565 affects projects using the pure-Python backend of the protobuf library with specific vulnerable versions.

4

What type of attack does CVE-2025-4565 enable?

CVE-2025-4565 enables denial of service attacks via recursive groups and messages in untrusted Protocol Buffers data.

5

What should I do if I cannot upgrade my protobuf package due to dependencies and I have CVE-2025-4565?

If you cannot upgrade due to dependencies, consider implementing strict input validation and limiting the size of Protocol Buffers data processed.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203