Skip to content
Fencer Vulns
medium 5.5

CVE-2021-37673 json

`CHECK`-fail in `MapStage` in TensorFlow

published 2021-08-12 5 y ago modified 2026-09-08 2 mo ago also BIT-tensorflow-2021-37673 , EUVD-2021-0399 , GHSA-278g-rq84-9hmg , PYSEC-2021-295 , PYSEC-2021-586 , PYSEC-2021-784

cvss
5.5
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 4%
public exploits
0
none known

Summary

TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.MapStage`. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L513) does not check that the `key` input is a valid non-empty tensor. We have patched the issue in GitHub commit d7de67733925de196ec8863a33445b73f9562d1d. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.

Patch / fix

  • pypi tensorflow 2.3.4, 2.4.3, 2.5.1
  • pypi tensorflow-cpu 2.3.4, 2.4.3, 2.5.1
  • pypi tensorflow-gpu 2.3.4, 2.4.3, 2.5.1
  • bitnami tensorflow 2.3.4, 2.4.3, 2.5.1
  • google tensorflow 2.3.4, 2.4.3
  • tensorflow2 Package Hub 15 SP3, openSUSE Leap 15.3 2.6.0-bp153.2.3.1
  • bazel3.7 Package Hub 15 SP3, openSUSE Leap 15.3 3.7.2-bp153.4.1
  • tensorflow2-lite Package Hub 15 SP3, openSUSE Leap 15.3 2.6.0-bp153.2.3.1
  • bazel-skylib1.0.3 Package Hub 15 SP3, openSUSE Leap 15.3 1.0.3-bp153.2.1
  • tensorflow2_2_6_0-gnu-hpc Package Hub 15 SP3, openSUSE Leap 15.3 2.6.0-bp153.2.3.1
  • tensorflow2_2_6_0-gnu-openmpi2-hpc Package Hub 15 SP3, openSUSE Leap 15.3 2.6.0-bp153.2.3.1

opensuse advisories openSUSE-SU-2022:10014-1

  • tensorflow Arch Linux 2.5.1-1

arch linux advisories AVG-2292

Exploit prediction

0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi tensorflow
<2.3.4
>=2.4.0, <2.4.3
>=2.5.0, <2.5.1
>=2.3.0, <2.3.4
2.3.4
2.4.3
2.5.1
pypi tensorflow-cpu
<2.3.4
>=2.4.0, <2.4.3
>=2.5.0, <2.5.1
>=2.3.0, <2.3.4
2.3.4
2.4.3
2.5.1
pypi tensorflow-gpu
<2.3.4
>=2.4.0, <2.4.3
>=2.5.0, <2.5.1
>=2.3.0, <2.3.4
2.3.4
2.4.3
2.5.1
bitnami tensorflow
>=2.3.0, <2.3.4
>=2.4.0, <2.4.3
>=2.5.0, <2.5.1
2.3.4
2.4.3
2.5.1

Affected products

  • tensorflow tensorflow

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Vulns 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.