Skip to content
Fencer Intel
high 7.0

CVE-2021-41206 json

Incomplete validation of shapes in multiple TF ops

published 5y ago modified 2mo ago also BIT-tensorflow-2021-41206 , EUVD-2021-0452 , GHSA-pgcq-h79j-2f69 , PYSEC-2021-843 , PYSEC-2021-845 , PYSEC-2021-847

cvss
7.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 7%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi tensorflow 2.4.4, 2.5.2, 2.6.1
  • pypi tensorflow-cpu 2.4.4, 2.5.2, 2.6.1
  • pypi tensorflow-gpu 2.4.4, 2.5.2, 2.6.1
  • bitnami tensorflow 2.4.4, 2.5.2, 2.6.1
  • google tensorflow 2.4.4, 2.5.2, 2.6.1
  • tensorflow Arch Linux 2.6.1-1

arch linux advisories AVG-2529

Is CVE-2021-41206 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 7.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P
OSV 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi tensorflow
>=2.6.0, <2.6.1
>=2.5.0, <2.5.2
<2.4.4
2.6.1
2.5.2
2.4.4
pypi tensorflow-cpu
>=2.6.0, <2.6.1
>=2.5.0, <2.5.2
<2.4.4
2.6.1
2.5.2
2.4.4
pypi tensorflow-gpu
>=2.6.0, <2.6.1
>=2.5.0, <2.5.2
<2.4.4
2.6.1
2.5.2
2.4.4
bitnami tensorflow
>=2.4.0, <2.4.4
>=2.5.0, <2.5.2
>=2.6.0, <2.6.1
2.4.4
2.5.2
2.6.1

Affected products

  • tensorflow tensorflow

Classification

Weakness
  • CWE-354 Improper Validation of Integrity Check Value

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.