All reports
Medium

Abort caused by allocating a vector that is too large 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 || >=2.6.0 <2.6.3
Fixed version
2.5.3 · 2.6.3
Affected versions
< 2.5.3
Fixed version
2.5.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-23580

Probability of exploitation in the next 30 days: 0.83%

FIRST EPSS · 2026-11-19

Description

Impact

During shape inference, TensorFlow can allocate a large vector based on a value from a tensor controlled by the user:

  const auto num_dims = Value(shape_dim);
  std::vector<DimensionHandle> dims;
  dims.reserve(num_dims);
Patches

We have patched the issue in GitHub commit 1361fb7e29449629e1df94d44e0427ebec8c83c7.

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.

Links