CVE-2022-1941: PYSEC-2026-899 - protobuf-cpp and protobuf-python have potential Denial of Service issue

Quick answers

Is CVE-2022-1941 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2022-1941 being exploited in the wild.

How severe is CVE-2022-1941?

Low severity, with a CVSS score of 3.1, published 7 July 2026.

Which products and versions are affected?

protobuf (PyPI) ECOSYSTEM:introduced=0,fixed=3.18.3, ECOSYSTEM:introduced=0,fixed=3.18.3,introduced=3.19.0,fixed=3.19.5,introduced=3.20.0,fixed=3.20.2,introduced=4.0.0,fixed=4.21.6.

Is there a fix for CVE-2022-1941?

Yes. protobuf (PyPI): upgrade to 3.18.3, 4.21.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2022-1941?

Check whether you run protobuf (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

• protobuf (PyPI): upgrade to 3.18.3, 4.21.6 or later

  pip install "protobuf>=4.21.6"

Affected products

• protobuf (PyPI) ECOSYSTEM:introduced=0,fixed=3.18.3, ECOSYSTEM:introduced=0,fixed=3.18.3,introduced=3.19.0,fixed=3.19.5,introduced=3.20.0,fixed=3.20.2,introduced=4.0.0,fixed=4.21.6

Identifiers

• CVE-2022-1941
• GHSA-8gq9-2x98-w8hf
• PYSEC-2026-899