All reports
High

Integer overflow in Tensorflow

Affected versions

Version ranges need review.

Affected versions
= 2.7.0
Fixed version
2.7.1
Affected versions
<2.5.3 || >=2.6.0 <2.6.3
Fixed version
2.5.3 · 2.6.3
Affected versions
>= 2.6.0, < 2.6.3
Fixed version
2.6.3
Affected versions
< 2.5.3
Fixed version
2.5.3
Affected versions
= 2.7.0
Fixed version
2.7.1
Affected versions
< 2.5.3
Fixed version
2.5.3
Affected versions
<2.5.3 || >=2.6.0 <2.6.3
Fixed version
2.5.3 · 2.6.3
Affected versions
>= 2.6.0, < 2.6.3
Fixed version
2.6.3
Affected versions
= 2.7.0
Fixed version
2.7.1
Affected versions
<2.5.3 || >=2.6.0 <2.6.3 || >=2.7.0 <2.7.1
Fixed version
2.5.3 · 2.6.3 · 2.7.1
Affected versions
< 2.5.3
Fixed version
2.5.3
Affected versions
>= 2.6.0, < 2.6.3
Fixed version
2.6.3

Exploitation

CVE-2022-23562

Probability of exploitation in the next 30 days: 0.58%

FIRST EPSS · 2026-11-19

Description

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 (merging #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 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.

Links