CVE-2021-41206

Incomplete validation of shapes in multiple TF ops

HIGH

7.8

CVSS Score

Published: November 5, 2021 at 10:05 PM UTC

Updated: June 17, 2026 at 04:08 AM UTC

2 products affected across 2 vendorsTensorflowTensorFlow

Using tensorflow by tensorflow?

Get instant alerts when new vulnerabilities affect tensorflow - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.8

Exploit prediction

EPSS 0.2%

Description

TensorFlow is an open source platform for machine learning. In affected versions several TensorFlow operations are missing validation for the shapes of the tensor arguments involved in the call. Depending on the API, this can result in undefined behavior and segfault or `CHECK`-fail related crashes but in some scenarios writes and reads from heap populated arrays are also possible. We have discovered these issues internally via tooling while working on improving/testing GPU op determinism. As such, we don't have reproducers and there will be multiple fixes for these issues. These fixes will be included in TensorFlow 2.7.0. We will also cherrypick these commits on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Tensorflow · Google

95%

2.4.0 ≤ v < 2.4.42.5.0 ≤ v < 2.5.22.6.0 ≤ v < 2.6.12.7.0 rc0 2.7.0 rc1

Affected range stops below 2.4.4, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.5.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.6.1, so it looks safe — our inference, not a vendor statement

TensorFlow · Tensorflow

60%

v < 2.4.4v < 2.5.2v < 2.6.1

Affected range stops below 2.4.4, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.5.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.6.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references