CVE-2021-37635 json
Heap out of bounds access in sparse reduction operations in TensorFlow
published 2021-08-12 5 y ago modified 2026-09-08 2 mo ago also BIT-tensorflow-2021-37635 , EUVD-2021-0361 , GHSA-cgfm-62j4-v4rf , PYSEC-2021-257 , PYSEC-2021-548 , PYSEC-2021-746
- cvss
- 7.3
- 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 6%
- public exploits
- 0
- none known
Summary
TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of sparse reduction operations in TensorFlow can trigger accesses outside of bounds of heap allocated data. The [implementation](https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_reduce_op.cc#L217-L228) fails to validate that each reduction group does not overflow and that each corresponding index does not point to outside the bounds of the input tensor. We have patched the issue in GitHub commit 87158f43f05f2720a374f3e6d22a7aaa3a33f750. 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.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H |
| GitHub | 3.1 | 7.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H |
| NVD | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
| NVD | 2.0 | 3.6 | AV:L/AC:L/Au:N/C:P/I:N/A:P |
| OSV | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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-125 Out-of-bounds Read
References
-
github.com
/tensorflow/tensorflow/commit/87158f43f05f2720a374f3e6d22a7aaa3a33f750
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/security/advisories/GHSA-cgfm-62j4-v4rf
web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-37635
advisory, web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-548.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-746.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-257.yaml
web
-
github.com
/tensorflow/tensorflow
package
Sources
- CVE List CVE-2021-37635
- GitHub Advisory GHSA-cgfm-62j4-v4rf
- NVD CVE-2021-37635
- OSV BIT-tensorflow-2021-37635
- OSV PYSEC-2021-257
- OSV PYSEC-2021-548
- OSV PYSEC-2021-746
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.