CVE-2022-29195: Denial of Service Vulnerability in TensorFlow

tensorflow Updated 02 Oct 2025

Summary

24/05/2022
Yes i
Moderate
5.5

CVE-2022-29195: Missing validation causes denial of service via StagePeek. Affects tensorflow across 3 version ranges.

< 2.6.4 >= 2.7.0, < 2.7.2 >= 2.8.0, < 2.8.1

Fixed in 2.6.4, 2.7.2 or 2.8.1, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2022-29195 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 Your last release was probably never penetration tested 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 open-source machine learning framework developed by Google. It provides a comprehensive ecosystem of tools, libraries, and resources for building and deploying machine learning models. TensorFlow is widely used in various domains, including research, industry, and academia. However, a vulnerability has been discovered in TensorFlow that can lead to a denial of service attack.

Vulnerability Detail

The vulnerability, identified as CVE-2022-29195, is caused by missing validation in the implementation of tf.raw_ops.StagePeek function. This function is used to peek at the contents of a TensorFlow stage. The code does not properly validate the input arguments, specifically the index parameter, which is assumed to be a scalar. As a result, an attacker can exploit this vulnerability by providing a malicious input, triggering a CHECK failure and causing a denial of service attack. The impact of this vulnerability can be significant, as it can disrupt the availability of TensorFlow-based applications and services.

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.6.4 2.6.4
    pip install --upgrade "tensorflow==2.6.4"
  • >= 2.7.0, < 2.7.2 2.7.2
    pip install --upgrade "tensorflow==2.7.2"
  • >= 2.8.0, < 2.8.1 2.8.1
    pip install --upgrade "tensorflow==2.8.1"

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 implement input validation before calling the tf.raw_ops.StagePeek function. This can be done by ensuring that the index parameter is a scalar value. Here is an example of how to perform the validation in Python:

import tensorflow as tf

index = tf.constant([], shape=[0], dtype=tf.int32)
if tf.rank(index) != 0:
    raise ValueError('Index must be a scalar')

# Call the StagePeek function
# ...

By validating the input, the vulnerability can be mitigated.

Conclusion

In conclusion, TensorFlow is affected by a denial of service vulnerability that can be exploited by providing a malicious input to the tf.raw_ops.StagePeek function. To mitigate the risk, it is crucial to update TensorFlow to the latest patched version. Implementing input validation can also help reduce the impact of this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for tensorflow →

Share this vulnerability

FAQ

The vulnerability can be exploited to trigger a denial of service attack, leading to the unavailability of TensorFlow-based applications and services.

To fix the vulnerability, it is recommended to update TensorFlow to the latest patched version (2.6.4, 2.7.2, or 2.8.1).

Yes, a workaround is to implement input validation before calling the vulnerable function. This can help mitigate the risk.

Yes, this vulnerability can be exploited remotely by providing a malicious input to the vulnerable function.

This vulnerability was reported by Neophytos Christou from Secure Systems Lab at Brown University.

Related vulnerabilities

Recent vulnerabilities recorded for tensorflow.

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.6.4 2.6.4
    pip install --upgrade "tensorflow==2.6.4"
  • >= 2.7.0, < 2.7.2 2.7.2
    pip install --upgrade "tensorflow==2.7.2"
  • >= 2.8.0, < 2.8.1 2.8.1
    pip install --upgrade "tensorflow==2.8.1"

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