# CVE-2022-23570: PYSEC-2026-3153 - Null-dereference in Tensorflow

Source: https://junglewise.ai/threats/cve-2022-23570-null-dereference-in-tensorflow  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-09  
License: CC BY 4.0 with a link back

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

Null-dereference in Tensorflow

Technologies: [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: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

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

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

**Which products and versions are affected?** tensorflow (PyPI) ECOSYSTEM:introduced=0,fixed=2.5.3, 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) ECOSYSTEM:introduced=0,fixed=2.5.3, GIT:introduced=0,fixed=8a513cec4bec15961fbfdedcaa5376522980455c|ECOSYSTEM:introduced=0,fixed=2.5.3,introduced=2.6.0,fixed=2.6.3; tensorflow-gpu (PyPI) ECOSYSTEM:introduced=0,fixed=2.5.3, GIT:introduced=0,fixed=8a513cec4bec15961fbfdedcaa5376522980455c|ECOSYSTEM:introduced=0,fixed=2.5.3,introduced=2.6.0,fixed=2.6.3.

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

**Am I affected by CVE-2022-23570?** Check whether you run tensorflow (PyPI), tensorflow-cpu (PyPI) or tensorflow-gpu (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

- tensorflow (PyPI): upgrade to 2.5.3, 2.7.1 or later

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

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

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

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

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


## Affected products

- tensorflow (PyPI) ECOSYSTEM:introduced=0,fixed=2.5.3, 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) ECOSYSTEM:introduced=0,fixed=2.5.3, GIT:introduced=0,fixed=8a513cec4bec15961fbfdedcaa5376522980455c|ECOSYSTEM:introduced=0,fixed=2.5.3,introduced=2.6.0,fixed=2.6.3
- tensorflow-gpu (PyPI) ECOSYSTEM:introduced=0,fixed=2.5.3, GIT:introduced=0,fixed=8a513cec4bec15961fbfdedcaa5376522980455c|ECOSYSTEM:introduced=0,fixed=2.5.3,introduced=2.6.0,fixed=2.6.3

## Identifiers

- CVE-2022-23570
- GHSA-9p77-mmrw-69c7
- PYSEC-2022-134
- PYSEC-2022-79
- PYSEC-2026-3153

## 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)