CVE-2021-37639: TensorFlow-CPU - Null Pointer Dereference and Heap Out-of-Bounds Read

tensorflow-cpu Updated 02 Oct 2025

Summary

12/08/2021
Yes i
Unrated
Not published

CVE-2021-37639: TensorFlow is an end-to-end open source platform for machine learning. Affects tensorflow-cpu across 3 version ranges.

>= 2.3.0, < 2.3.4 >= 2.4.0, < 2.4.3 < 9e82dce6e6bd1f36a57e08fa85af213e2b2f2622

Fixed in 2.3.4 or 2.4.3, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2021-37639 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

TensorFlow is an end-to-end open source platform for machine learning. It provides a comprehensive ecosystem of tools, libraries, and resources for building 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 domains for developing and deploying machine learning applications.

Vulnerability Detail

The vulnerability (CVE-2021-37639) in TensorFlow-CPU arises when restoring tensors via raw APIs. If the tensor name is not provided, TensorFlow can be tricked into dereferencing a null pointer. Additionally, attackers can read memory outside the bounds of heap allocated data by providing some tensor names but not enough for a successful restoration. This vulnerability can lead to undefined behavior, null pointer dereference, or heap out-of-bounds read. The issue has been patched in the latest GitHub commit (9e82dce6e6bd1f36a57e08fa85af213e2b2f2622) and will be included in TensorFlow 2.6.0. The fix will also be backported to TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4.

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.3.0, < 2.3.4 2.3.4
    pip install --upgrade "tensorflow-cpu==2.3.4"
  • >= 2.4.0, < 2.4.3 2.4.3
    pip install --upgrade "tensorflow-cpu==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 mentioned for this vulnerability. It is recommended to apply the fix as described in the 'how_to_fix' section.

Conclusion

The vulnerability (CVE-2021-37639) in TensorFlow-CPU can lead to null pointer dereference or heap out-of-bounds read. It is crucial to update to the latest version or apply the provided patch to mitigate the risk. For further support and assistance in vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for tensorflow-cpu →

Share this vulnerability

FAQ

TensorFlow is an open source platform for machine learning that provides a comprehensive set of tools, libraries, and resources for building and deploying machine learning models.

TensorFlow-CPU is a specific package that focuses on running TensorFlow on CPUs. It is widely used for developing and deploying machine learning applications on CPU-based systems.

This vulnerability can lead to undefined behavior, null pointer dereference, or heap out-of-bounds read in TensorFlow-CPU. It could potentially be exploited by attackers to cause a denial-of-service or leak sensitive information from memory.

To fix the vulnerability, update TensorFlow-CPU to the latest version (2.6.0) once it is released. Alternatively, you can apply the patch by cherry-picking the specific commit (9e82dce6e6bd1f36a57e08fa85af213e2b2f2622) from the GitHub repository.

Yes, TensorFlow versions 2.5.1, 2.4.3, and 2.3.4 are also affected by this vulnerability. The fix will be backported to these versions as well.

Related vulnerabilities

Recent vulnerabilities recorded for tensorflow-cpu.

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.3.0, < 2.3.4 2.3.4
    pip install --upgrade "tensorflow-cpu==2.3.4"
  • >= 2.4.0, < 2.4.3 2.4.3
    pip install --upgrade "tensorflow-cpu==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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback