CVE-2021-29541: TensorFlow-CPU Null Pointer Dereference in StringNGrams
Summary
CVE-2021-29541: TensorFlow is an end-to-end open source platform for machine learning. Affects tensorflow-cpu across 5 version ranges.
< 2.1.4
>= 2.2.0, < 2.2.3
>= 2.3.0, < 2.3.3
>= 2.4.0, < 2.4.2
< ba424dd8f16f7110eea526a8086f1a155f14f22b
Fixed in 4 releases; the minimum fixed version depends on the release line you run. How to fix ↓
Also tracked for
- tensorflow · Bitnami
- tensorflow · PyPI
- tensorflow · PyPI
- tensorflow-gpu · PyPI
The same CVE-2021-29541 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-CPU is a specific package that focuses on running TensorFlow on CPUs. It is widely used in various industries and research fields for machine learning tasks.
Vulnerability Detail
The vulnerability (CVE-2021-29541) exists in the tf.raw_ops.StringNGrams function of TensorFlow-CPU. An attacker can exploit this vulnerability by providing a malicious input that triggers a null pointer dereference. The issue arises due to incomplete validation of the data_splits argument in the implementation of StringNGrams. As a result, when the output is computed to have a size of 0 or negative, the ngrams_data pointer becomes null. Subsequent writes to the output tensor then lead to a null pointer dereference. This vulnerability can potentially be exploited to cause a denial-of-service (DoS) condition or execute arbitrary code.
How To Fix
Latest published version: 2.21.0 as of 22 Oct 2026
pip install --upgrade "tensorflow-cpu==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.1.42.1.4pip install --upgrade "tensorflow-cpu==2.1.4" -
>= 2.2.0, < 2.2.32.2.3pip install --upgrade "tensorflow-cpu==2.2.3" -
>= 2.3.0, < 2.3.32.3.3pip install --upgrade "tensorflow-cpu==2.3.3" -
>= 2.4.0, < 2.4.22.4.2pip install --upgrade "tensorflow-cpu==2.4.2"
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
As a workaround, users can avoid using the tf.raw_ops.StringNGrams function until they have updated their TensorFlow-CPU installation to a fixed version. By refraining from using this specific function, the vulnerability can be temporarily mitigated.
Conclusion
In conclusion, the vulnerability (CVE-2021-29541) in TensorFlow-CPU's tf.raw_ops.StringNGrams function can lead to a null pointer dereference, potentially resulting in a denial-of-service (DoS) condition or arbitrary code execution. It is crucial to update to the fixed versions of TensorFlow-CPU or apply the provided workarounds to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for tensorflow-cpu →
FAQ
TensorFlow is an open source platform for machine learning that provides a comprehensive set of tools and resources for developing and deploying machine learning models.
TensorFlow-CPU is a specific package that focuses on running TensorFlow on CPUs. It is widely used for machine learning tasks in various industries and research fields.
This vulnerability can potentially be exploited to cause a denial-of-service (DoS) condition or execute arbitrary code. It is important to update to the fixed versions of TensorFlow-CPU to mitigate the risk.
To fix this vulnerability, it is recommended to update your TensorFlow-CPU installation to the latest version once it becomes available. Alternatively, you can upgrade to one of the fixed versions (TensorFlow 2.5.0, TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3, or TensorFlow 2.1.4).
Yes, you can temporarily mitigate the risk by avoiding the use of the tf.raw_ops.StringNGrams function until you have updated your TensorFlow-CPU installation to a fixed version.
References
Related vulnerabilities
Recent vulnerabilities recorded for tensorflow-cpu.