CVE-2021-29619: TensorFlow CPU - Segfault in tf.raw_ops.SparseCountSparseOutput

tensorflow-cpu Updated 02 Oct 2025

Summary

14/05/2021
Yes i
Unrated
Not published

CVE-2021-29619: 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 < 82e6203221865de4008445b13c69b6826d2b28d9

Fixed in 4 releases; the minimum fixed version depends on the release line you run. How to fix ↓

Also tracked for

The same CVE-2021-29619 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 developing and deploying machine learning models. TensorFlow is widely used in various domains, including research, industry, and academia. The vulnerability affects the 'tensorflow-cpu' package, which is a Python package for running TensorFlow on CPUs. This package is commonly used when GPU acceleration is not available or required.

Vulnerability Detail

The vulnerability (CVE-2021-29619) arises when invalid arguments are passed to the 'tf.raw_ops.SparseCountSparseOutput' function in TensorFlow. This issue can be triggered by providing malformed inputs, such as those discovered through fuzzing techniques. As a result, a segmentation fault (segfault) occurs, leading to a crash of the TensorFlow application. The impact of this vulnerability can range from denial of service (DoS) to potential remote code execution (RCE) if an attacker can control the inputs to the vulnerable function. The vulnerability has been addressed in TensorFlow 2.5.0, and patches have been backported to earlier versions (2.4.2, 2.3.3, 2.2.3, and 2.1.4) that are still within the supported range.

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.4 2.1.4
    pip install --upgrade "tensorflow-cpu==2.1.4"
  • >= 2.2.0, < 2.2.3 2.2.3
    pip install --upgrade "tensorflow-cpu==2.2.3"
  • >= 2.3.0, < 2.3.3 2.3.3
    pip install --upgrade "tensorflow-cpu==2.3.3"
  • >= 2.4.0, < 2.4.2 2.4.2
    pip 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

There is no known workaround for this vulnerability. It is essential to update the 'tensorflow-cpu' package to the fixed version or apply the provided patches to mitigate the risk of exploitation.

Conclusion

The vulnerability (CVE-2021-29619) in TensorFlow CPU, specifically in the 'tf.raw_ops.SparseCountSparseOutput' function, can lead to a segfault and potential application crashes. It is recommended to update the 'tensorflow-cpu' package to the latest version (2.5.0) or apply the provided patches for earlier versions (2.4.2, 2.3.3, 2.2.3, or 2.1.4) to mitigate the risk. For further support and assistance on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for tensorflow-cpu →

Share this vulnerability

FAQ

TensorFlow is an open source platform for machine learning that provides tools and libraries for developing and deploying machine learning models.

The 'tensorflow-cpu' package is a Python package that allows running TensorFlow on CPUs when GPU acceleration is not available or required.

The vulnerability can lead to a segmentation fault (segfault) in TensorFlow, causing the application to crash. Depending on the attacker's ability to control inputs, it may also result in denial of service (DoS) or potential remote code execution (RCE).

To fix this vulnerability, update the 'tensorflow-cpu' package to the latest version (2.5.0) or apply the provided patches for earlier versions (2.4.2, 2.3.3, 2.2.3, or 2.1.4).

No, there is no known workaround for this vulnerability. It is crucial to update the package to the fixed version or apply the provided patches.

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.1.4 2.1.4
    pip install --upgrade "tensorflow-cpu==2.1.4"
  • >= 2.2.0, < 2.2.3 2.2.3
    pip install --upgrade "tensorflow-cpu==2.2.3"
  • >= 2.3.0, < 2.3.3 2.3.3
    pip install --upgrade "tensorflow-cpu==2.3.3"
  • >= 2.4.0, < 2.4.2 2.4.2
    pip 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 →

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