CVE-2021-29540: TensorFlow Heap Buffer Overflow in Conv2DBackpropFilter
Summary
CVE-2021-29540: TensorFlow is an end-to-end open source platform for machine learning. Affects tensorflow across 5 version ranges.
>= 2.2.0, < 2.3.0rc0
< 2.2.0rc0
>= 2.3.0, < 2.3.4
>= 2.4.0, < 2.4.3
< c570e2ecfc822941335ad48f6e10df4e21f11c96
Fixed in 4 releases; the minimum fixed version depends on the release line you run. How to fix ↓
Also tracked for
- tensorflow · Bitnami
- tensorflow-cpu · PyPI
- tensorflow-gpu · PyPI
The same CVE-2021-29540 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
TensorFlow is an end-to-end open source platform for machine learning. It provides a comprehensive ecosystem of tools, libraries, and resources for developing and deploying machine learning models. TensorFlow is widely used in various industries and research domains for tasks such as image recognition, natural language processing, and recommendation systems. However, a vulnerability has been discovered in TensorFlow that can lead to a heap buffer overflow in the Conv2DBackpropFilter function.
Vulnerability Detail
The vulnerability arises due to a lack of validation in the computation of the filter tensor size in the Conv2DBackpropFilter implementation. The code fails to verify that the computed size matches the number of elements in the filter_sizes tensor. As a result, when reading or writing to the buffer, the code uses the computed size instead of the actual number of elements. This can lead to a heap buffer overflow, potentially allowing an attacker to execute arbitrary code or cause a denial-of-service condition. The vulnerability has been assigned the identifier CVE-2021-29540.
How To Fix
Latest published version: 2.21.0 as of 22 Oct 2026
pip install --upgrade "tensorflow==2.21.0"Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 2.2.0rc02.2.0rc0pip install --upgrade "tensorflow==2.2.0rc0" -
>= 2.2.0, < 2.3.0rc02.3.0rc0pip install --upgrade "tensorflow==2.3.0rc0" -
>= 2.3.0, < 2.3.42.3.4pip install --upgrade "tensorflow==2.3.4" -
>= 2.4.0, < 2.4.32.4.3pip install --upgrade "tensorflow==2.4.3"
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no specific workaround provided for this vulnerability. It is recommended to apply the fix by upgrading to the patched versions of TensorFlow.
Conclusion
The vulnerability in TensorFlow's Conv2DBackpropFilter function can result in a heap buffer overflow, potentially leading to arbitrary code execution or denial-of-service. It is crucial to upgrade to the patched versions of TensorFlow or apply the fix as soon as possible. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for tensorflow →
FAQ
TensorFlow is an open source platform for machine learning that provides a comprehensive set of tools and libraries for developing and deploying machine learning models.
A heap buffer overflow occurs when a program writes more data to a buffer in the heap memory than the buffer can hold. This can lead to memory corruption and potentially allow an attacker to execute arbitrary code or cause a crash.
You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your Pipfile.lock and the playground will analyze it for any open-source vulnerabilities, including this TensorFlow vulnerability.
No, not all versions of TensorFlow are affected. The vulnerability has been identified in versions 2.1.4 and above. It has been fixed in TensorFlow 2.5.0 and backported to versions 2.4.2, 2.3.3, 2.2.3, and 2.1.4.
There is no known exploit for this vulnerability at the time of this report. However, it is important to apply the fix as soon as possible to mitigate the risk.
References
Related vulnerabilities
Recent vulnerabilities recorded for tensorflow.
