---
id: CVE-2022-23562
aliases:
  - GHSA-qx3f-p745-w4hr
  - BIT-tensorflow-2022-23562
  - PYSEC-2022-126
  - PYSEC-2022-71
  - PYSEC-2026-3232
title: Integer overflow in Tensorflow
summary: Integer overflow in Tensorflow
severity: high
cvss: 7.6
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H'
vendor: tensorflow
product: tensorflow
ecosystem: pip
affected:
  - tensorflow < 2.5.3
  - 'tensorflow >= 2.6.0, < 2.6.3'
  - 'tensorflow >= 2.7.0, < 2.7.1'
  - tensorflow-cpu < 2.5.3
  - 'tensorflow-cpu >= 2.6.0, < 2.6.3'
  - 'tensorflow-cpu >= 2.7.0, < 2.7.1'
  - tensorflow-gpu < 2.5.3
  - 'tensorflow-gpu >= 2.6.0, < 2.6.3'
  - 'tensorflow-gpu >= 2.7.0, < 2.7.1'
patched:
  - tensorflow 2.5.3
  - tensorflow 2.6.3
  - tensorflow 2.7.1
  - tensorflow-cpu 2.5.3
  - tensorflow-cpu 2.6.3
  - tensorflow-cpu 2.7.1
  - tensorflow-gpu 2.5.3
  - tensorflow-gpu 2.6.3
  - tensorflow-gpu 2.7.1
published: '2022-02-09'
updated: '2026-07-13'
source: OSV
sourceUrl: 'https://osv.dev/vulnerability/GHSA-qx3f-p745-w4hr'
references:
  - url: >-
      https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qx3f-p745-w4hr
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2022-23562'
  - url: 'https://github.com/tensorflow/tensorflow/issues/52676'
  - url: 'https://github.com/tensorflow/tensorflow/pull/51733'
  - url: >-
      https://github.com/tensorflow/tensorflow/commit/f0147751fd5d2ff23251149ebad9af9f03010732
  - url: >-
      https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2022-71.yaml
  - url: >-
      https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2022-126.yaml
  - url: 'https://github.com/tensorflow/tensorflow'
tags:
  - osv
  - pip
epss: 0.00583
epssPercentile: 0.45482
ingestedAt: '2026-07-13T18:58:02.322Z'
---

## Overview

### Impact
The implementation of `Range` suffers from integer overflows. These can trigger undefined behavior or, in some scenarios, extremely large allocations.

### Patches
We have patched the issue in GitHub commit [f0147751fd5d2ff23251149ebad9af9f03010732](https://github.com/tensorflow/tensorflow/commit/f0147751fd5d2ff23251149ebad9af9f03010732) (merging [#51733](https://github.com/tensorflow/tensorflow/pull/51733)).

The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/52676).

## Affected packages

- `tensorflow < 2.5.3`
- `tensorflow >= 2.6.0, < 2.6.3`
- `tensorflow >= 2.7.0, < 2.7.1`
- `tensorflow-cpu < 2.5.3`
- `tensorflow-cpu >= 2.6.0, < 2.6.3`
- `tensorflow-cpu >= 2.7.0, < 2.7.1`
- `tensorflow-gpu < 2.5.3`
- `tensorflow-gpu >= 2.6.0, < 2.6.3`
- `tensorflow-gpu >= 2.7.0, < 2.7.1`

## Remediation

Upgrade to a patched release:

- `tensorflow 2.5.3`
- `tensorflow 2.6.3`
- `tensorflow 2.7.1`
- `tensorflow-cpu 2.5.3`
- `tensorflow-cpu 2.6.3`
- `tensorflow-cpu 2.7.1`
- `tensorflow-gpu 2.5.3`
- `tensorflow-gpu 2.6.3`
- `tensorflow-gpu 2.7.1`