Skip to content
Fencer Vulns
medium 5.5

CVE-2021-41195 json

Crash in `tf.math.segment_*` operations

published 2021-11-05 5 y ago modified 2026-09-08 2 mo ago also BIT-tensorflow-2021-41195 , EUVD-2021-0451 , GHSA-cq76-mxrc-vchh , PYSEC-2021-842 , PYSEC-2021-844 , PYSEC-2021-846

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 11%
public exploits
0
none known

Summary

TensorFlow is an open source platform for machine learning. In affected versions the implementation of `tf.math.segment_*` operations results in a `CHECK`-fail related abort (and denial of service) if a segment id in `segment_ids` is large. This is similar to CVE-2021-29584 (and similar other reported vulnerabilities in TensorFlow, localized to specific APIs): the implementation (both on CPU and GPU) computes the output shape using `AddDim`. However, if the number of elements in the tensor overflows an `int64_t` value, `AddDim` results in a `CHECK` failure which provokes a `std::abort`. Instead, code should use `AddDimWithStatus`. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit 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

Exploit prediction

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

Exploits and checks

  • github.com https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cq76-mxrc-vchh referenced PoC, tagged "exploit" by a source, unverified

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.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.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-190 Integer Overflow or Wraparound

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.