Bug 2432398 (CVE-2026-0994)

Summary: CVE-2026-0994 python: protobuf: Protobuf: Denial of Service due to recursion depth bypass
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: ataylor, eglynn, jjoyce, jschluet, kshier, lhh, mburns, mgarciac, stcannon, teagle
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in protobuf. A remote attacker can exploit this denial-of-service (DoS) vulnerability by supplying deeply nested `google.protobuf.Any` messages to the `google.protobuf.json_format.ParseDict()` function. This bypasses the intended recursion depth limit, leading to the exhaustion of Python’s recursion stack and causing a `RecursionError`, which results in a denial of service.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2432842, 2432843, 2432844, 2432845    
Bug Blocks:    

Description OSIDB Bzimport 2026-01-23 16:03:26 UTC
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.

Comment 2 errata-xmlrpc 2026-02-23 08:24:36 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.4 Extended Update Support

Via RHSA-2026:3059 https://access.redhat.com/errata/RHSA-2026:3059

Comment 3 errata-xmlrpc 2026-02-23 15:40:24 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:3094 https://access.redhat.com/errata/RHSA-2026:3094

Comment 4 errata-xmlrpc 2026-02-23 15:59:10 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions

Via RHSA-2026:3097 https://access.redhat.com/errata/RHSA-2026:3097

Comment 5 errata-xmlrpc 2026-02-23 16:13:28 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:3095 https://access.redhat.com/errata/RHSA-2026:3095

Comment 6 errata-xmlrpc 2026-02-24 15:31:08 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10.0 Extended Update Support

Via RHSA-2026:3218 https://access.redhat.com/errata/RHSA-2026:3218

Comment 7 errata-xmlrpc 2026-02-24 16:05:21 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions

Via RHSA-2026:3220 https://access.redhat.com/errata/RHSA-2026:3220

Comment 8 errata-xmlrpc 2026-02-24 16:19:18 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.6 Extended Update Support

Via RHSA-2026:3219 https://access.redhat.com/errata/RHSA-2026:3219

Comment 9 errata-xmlrpc 2026-03-06 10:13:29 UTC
This issue has been addressed in the following products:

  Red Hat Ansible Automation Platform 2.6 for RHEL 9
  Red Hat Ansible Automation Platform 2.6 for RHEL 10

Via RHSA-2026:3958 https://access.redhat.com/errata/RHSA-2026:3958

Comment 10 errata-xmlrpc 2026-03-06 10:55:37 UTC
This issue has been addressed in the following products:

  Red Hat Ansible Automation Platform 2.5 for RHEL 8
  Red Hat Ansible Automation Platform 2.5 for RHEL 9

Via RHSA-2026:3959 https://access.redhat.com/errata/RHSA-2026:3959