Quick answers
- Is CVE-2022-29193 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-29193 being exploited in the wild.
- How severe is CVE-2022-29193?
- Low severity, with a CVSS score of 3.1, published 6 July 2026.
- Which products and versions are affected?
- Google TensorFlow 0.x through 2.6.3, 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-29193?
- 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-29193 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2022-29193?
- 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 tf.raw_ops.TensorSummaryV2 operation does not validate that the `serialized_summary_metadata` input parameter is a scalar tensor before calling `.scalar<tstring>()()` on it. An attacker can pass a non-scalar tensor (such as an empty array) which causes a CHECK-failure assertion and crashes the process. The vulnerability requires the attacker to be able to call TensorFlow operations directly, which typically means network or local access to a system running TensorFlow with exposed APIs. The issue is a missing input validation (CWE-20) that enables denial of service. Patches are available in TensorFlow 2.6.4, 2.7.2, 2.8.1, and 2.9.0+.
Affected products
- Google TensorFlow 0.x through 2.6.3, 2.7.0-2.7.1, 2.8.0
- Google TensorFlow-CPU 1.15.0, 2.1.0 through 2.6.3, 2.7.0-2.7.1, 2.8.0
- Google TensorFlow-GPU 1.15.0, 2.1.0 through 2.6.3, 2.7.0-2.7.1, 2.8.0
Identifiers
- CVE-2022-29193
- GHSA-2p9q-h29j-3f5v
- PYSEC-2026-3087
- PYSEC-2026-3265
- PYSEC-2026-942
Timeline
- 2022-05-20: disclosed
- 2022-05-24: patched: Fix committed to main branch (commit 290bb05c80c327ed74fae1d089f1001b1e2a4ef7)
- 2022-06: patched: Patches released in TensorFlow 2.6.4, 2.7.2, 2.8.1, and 2.9.0