# CVE-2022-21729: PYSEC-2026-3090 - Overflow and uncaught divide by zero in Tensorflow

Source: https://junglewise.ai/threats/cve-2022-21729-tensorflow-integer-overflow-and-divide-by-zero-in-unravelindex  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-09. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2022-21729 · Severity: low · CVSS 3.1 · Published 2026-07-09

TensorFlow's UnravelIndex operation, a utility function used to convert flat indices into multidimensional coordinates, is vulnerable to a division by zero error triggered by integer overflow. An attacker with the ability to call this operation directly can crash a TensorFlow application, causing denial of service and disrupting machine learning inference or training workloads.

Technologies: [Google TensorFlow](https://junglewise.ai/threats/technologies/tensorflow), [tensorflow (PyPI)](https://junglewise.ai/threats/technologies/pypi-tensorflow), [tensorflow-cpu (PyPI)](https://junglewise.ai/threats/technologies/tensorflow-cpu), [tensorflow-gpu (PyPI)](https://junglewise.ai/threats/technologies/tensorflow-gpu). Vendors: [Google](https://junglewise.ai/threats/vendors/google), [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2022-21729 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2022-21729 being exploited in the wild.

**How severe is CVE-2022-21729?** Low severity, with a CVSS score of 3.1, published 9 July 2026.

**Which products and versions are affected?** Google TensorFlow all versions before 2.5.3, 2.6.x before 2.6.3, 2.7.0; tensorflow (PyPI) ECOSYSTEM:introduced=0,fixed=2.5.3,introduced=2.6.0,fixed=2.6.3,introduced=2.7.0,fixed=2.7.1; tensorflow-cpu (PyPI) GIT:introduced=0,fixed=58b34c6c8250983948b5a781b426f6aa01fd47af|ECOSYSTEM:introduced=0,fixed=2.5.3,introduced=2.6.0,fixed=2.6.3; tensorflow-gpu (PyPI) GIT:introduced=0,fixed=58b34c6c8250983948b5a781b426f6aa01fd47af|ECOSYSTEM:introduced=0,fixed=2.5.3,introduced=2.6.0,fixed=2.6.3.

**Is there a fix for CVE-2022-21729?** Yes. tensorflow (PyPI): upgrade to 2.7.1 or later; tensorflow-cpu (PyPI): upgrade to 2.6.3 or later; tensorflow-gpu (PyPI): upgrade to 2.6.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2022-21729 attacked?** It is attacked over the network.

**Am I affected by CVE-2022-21729?** 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.7.1 or later

  ```sh
  pip install "tensorflow>=2.7.1"
  ```

- tensorflow-cpu (PyPI): upgrade to 2.6.3 or later

  ```sh
  pip install "tensorflow-cpu>=2.6.3"
  ```

- tensorflow-gpu (PyPI): upgrade to 2.6.3 or later

  ```sh
  pip install "tensorflow-gpu>=2.6.3"
  ```


## Technical details

The vulnerability exists in the UnravelIndex operation due to an integer overflow (CWE-190) that leads to an uncaught division by zero. The flaw occurs when processing specially crafted negative indices and dimension parameters, as demonstrated in the proof of concept: `tf.raw_ops.UnravelIndex(indices=-0x100000, dims=[0x100000, 0x100000])`. The attack requires direct access to call TensorFlow operations, typically achievable only by applications that accept untrusted model code or tensor inputs. Successful exploitation causes an unhandled exception that terminates the process. Patches are available in TensorFlow 2.5.3, 2.6.3, 2.7.1, and 2.8.0+.

## Affected products

- Google TensorFlow all versions before 2.5.3, 2.6.x before 2.6.3, 2.7.0

## Identifiers

- CVE-2022-21729
- GHSA-34f9-hjfq-rr8j
- PYSEC-2022-108
- PYSEC-2022-53
- PYSEC-2026-3090

## Timeline

- 2022-02-02: disclosed
- 2022-02-10: patched: Patches released for 2.5.3, 2.6.3, 2.7.1; fix included in 2.8.0

## References

- [https://github.com/tensorflow/tensorflow/security/advisories/GHSA-34f9-hjfq-rr8j](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-34f9-hjfq-rr8j)

## Related threats

- [PYSEC-2026-3331 - TensorFlow has segfault in array_ops.upper_bound](https://junglewise.ai/threats/cve-2023-33976-tensorflow-has-segfault-in-array-ops-upper-bound)
- [PYSEC-2026-3182 - TensorFlow Denial of Service vulnerability](https://junglewise.ai/threats/cve-2023-25661-tensorflow-denial-of-service-vulnerability)
- [PYSEC-2026-3300 - TensorFlow vulnerable to Out-of-Bounds Read in DynamicStitch](https://junglewise.ai/threats/cve-2023-25659-tensorflow-vulnerable-to-out-of-bounds-read-in-dynamicstitch)
- [PYSEC-2026-3362 - TensorFlow vulnerable to seg fault in `tf.raw_ops.Print`](https://junglewise.ai/threats/cve-2023-25660-tensorflow-vulnerable-to-seg-fault-in-tf-raw-ops-print)
- [PYSEC-2026-3293 - TensorFlow vulnerable to integer overflow in EditDistance](https://junglewise.ai/threats/cve-2023-25662-tensorflow-vulnerable-to-integer-overflow-in-editdistance)