Quick answers
- Is CVE-2022-29200 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-29200 being exploited in the wild.
- How severe is CVE-2022-29200?
- Low severity, with a CVSS score of 3.1, published 6 July 2026.
- Which products and versions are affected?
- Google TensorFlow before 2.6.4, 2.7.0–2.7.1, 2.8.0; tensorflow (PyPI) ECOSYSTEM:introduced=0,fixed=2.6.4,introduced=2.7.0,fixed=2.7.2,introduced=2.8.0,fixed=2.8.1; tensorflow-cpu (PyPI) ECOSYSTEM:introduced=0,fixed=2.6.4,introduced=2.7.0,fixed=2.7.2,introduced=2.8.0,fixed=2.8.1; tensorflow-gpu (PyPI) ECOSYSTEM:introduced=0,fixed=2.6.4,introduced=2.7.0,fixed=2.7.2,introduced=2.8.0,fixed=2.8.1.
- Is there a fix for CVE-2022-29200?
- Yes. tensorflow (PyPI): upgrade to 2.8.1 or later; tensorflow-cpu (PyPI): upgrade to 2.8.1 or later; tensorflow-gpu (PyPI): upgrade to 2.8.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-29200 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2022-29200?
- Check whether you run Google TensorFlow, tensorflow (PyPI), tensorflow-cpu (PyPI) or one of the others listed 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
- tensorflow (PyPI): upgrade to 2.8.1 or later
pip install "tensorflow>=2.8.1" - tensorflow-cpu (PyPI): upgrade to 2.8.1 or later
pip install "tensorflow-cpu>=2.8.1" - tensorflow-gpu (PyPI): upgrade to 2.8.1 or later
pip install "tensorflow-gpu>=2.8.1"
Technical details
The vulnerability exists in tf.raw_ops.LSTMBlockCell, which fails to validate the rank (number of dimensions) of input tensors before processing them. The vulnerability is a missing input validation issue (CWE-20) that allows a local attacker to craft a Python script with malformed tensor dimensions and trigger a CHECK-failure during element access. The attack requires direct access to a TensorFlow process or application that calls LSTMBlockCell; no network access or authentication bypass is needed. An attacker achieves denial of service by crashing the process, not code execution or data compromise. Fixes were released in TensorFlow 2.6.4, 2.7.2, 2.8.1, and 2.9.0.
Affected products
- Google TensorFlow before 2.6.4, 2.7.0–2.7.1, 2.8.0
- Google TensorFlow CPU before 2.6.4, 2.7.0–2.7.1, 2.8.0
- Google TensorFlow GPU before 2.6.4, 2.7.0–2.7.1, 2.8.0
Identifiers
- CVE-2022-29200
- GHSA-2vv3-56qg-g2cf
- PYSEC-2026-3089
- PYSEC-2026-3267
- PYSEC-2026-944
Timeline
- 2022-05-17: disclosed
- 2022-05-24: advisory
- 2022-05-24: patched: Patched in TensorFlow 2.6.4, 2.7.2, 2.8.1, and 2.9.0