CVE-2021-29586 json
Division by zero in optimized pooling implementations in TFLite
published 2021-05-14 5 y ago modified 2026-09-08 2 mo ago also BIT-tensorflow-2021-29586 , EUVD-2021-0327 , GHSA-26j7-6w8w-7922 , PYSEC-2021-223 , PYSEC-2021-514 , PYSEC-2021-712
- cvss
- 2.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 10%
- public exploits
- 0
- none known
Summary
TensorFlow is an end-to-end open source platform for machine learning. Optimized pooling implementations in TFLite fail to check that the stride arguments are not 0 before calling `ComputePaddingHeightWidth`(https://github.com/tensorflow/tensorflow/blob/3f24ccd932546416ec906a02ddd183b48a1d2c83/tensorflow/lite/kernels/pooling.cc#L90). Since users can craft special models which will have `params->stride_{height,width}` be zero, this will result in a division by zero. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
Patch / fix
- pypi tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2
- pypi tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2
- pypi tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2
- bitnami tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2
- google tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2
- tensorflow Arch Linux 2.5.0-1
arch linux advisories AVG-1962
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/tensorflow/tensorflow/security/advisories/GHSA-26j7-6w8w-7922 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 2.5 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L |
| GitHub | 3.1 | 2.5 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L |
| 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.1.4 >=2.2.0, <2.2.3 >=2.3.0, <2.3.3 >=2.4.0, <2.4.2 |
2.1.4 2.2.3 2.3.3 2.4.2 |
| pypi | tensorflow-cpu | <2.1.4 >=2.2.0, <2.2.3 >=2.3.0, <2.3.3 >=2.4.0, <2.4.2 |
2.1.4 2.2.3 2.3.3 2.4.2 |
| pypi | tensorflow-gpu | <2.1.4 >=2.2.0, <2.2.3 >=2.3.0, <2.3.3 >=2.4.0, <2.4.2 |
2.1.4 2.2.3 2.3.3 2.4.2 |
| bitnami | tensorflow | <2.1.4 >=2.2.0, <2.2.3 >=2.3.0, <2.3.3 >=2.4.0, <2.4.2 |
2.1.4 2.2.3 2.3.3 2.4.2 |
Affected products
- tensorflow tensorflow
Classification
- Weakness
-
- CWE-369 Divide By Zero
References
-
github.com
/tensorflow/tensorflow/commit/5f7975d09eac0f10ed8a17dbb6f5964977725adc
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/security/advisories/GHSA-26j7-6w8w-7922
web, exploit, patch, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-29586
advisory, web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-514.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-712.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-223.yaml
web
-
github.com
/tensorflow/tensorflow
package
-
github.com
/tensorflow/tensorflow/blob/3f24ccd932546416ec906a02ddd183b48a1d2c83/tensorflow/lite/kernels/pooling.cc#L90
web
Sources
- CVE List CVE-2021-29586
- GitHub Advisory GHSA-26j7-6w8w-7922
- NVD CVE-2021-29586
- OSV BIT-tensorflow-2021-29586
- OSV PYSEC-2021-223
- OSV PYSEC-2021-514
- OSV PYSEC-2021-712
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.