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

tensorflow Updated 02 Oct 2025

Summary

24/05/2022
Yes i
Moderate
5.5

CVE-2022-29196: Missing validation causes denial of service via Conv3DBackpropFilterV2. 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-29196 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

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 could lead to a denial of service attack.

Vulnerability Detail

The vulnerability, identified as CVE-2022-29196, is caused by missing validation in the implementation of tf.raw_ops.Conv3DBackpropFilterV2 function in TensorFlow. This function is responsible for backpropagation of the filter in a 3D convolutional neural network. The issue arises due to the lack of validation for the filter_sizes argument, allowing an attacker to trigger a CHECK-failure and exploit it for a denial of service attack. By providing malicious input, an attacker can crash the system or make it unresponsive.

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 temporary workaround, users can implement input validation for the filter_sizes argument in their own code. By ensuring that the argument is a valid vector, the vulnerability can be mitigated. Here is an example of how to perform the validation in Python:

import tensorflow as tf

filter_sizes = [1, 2, 3, 4]  # Example filter sizes

if not isinstance(filter_sizes, list):
    raise ValueError('filter_sizes must be a list')

# Use the validated filter_sizes in the Conv3DBackpropFilterV2 function
# ... (rest of the code)

It is important to note that this workaround is not a permanent solution and should be replaced with the official patch as soon as possible.

Conclusion

In conclusion, the vulnerability in TensorFlow's Conv3DBackpropFilterV2 function can be exploited to trigger a denial of service attack. Users are advised to update their TensorFlow installation to one of the patched versions (2.6.4, 2.7.2, 2.8.1) or wait for the upcoming release of TensorFlow 2.9.0. As a temporary workaround, input validation can be implemented for the filter_sizes argument. For further support and assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for tensorflow →

Share this vulnerability

FAQ

The vulnerability allows an attacker to trigger a denial of service attack by exploiting the missing validation in TensorFlow's Conv3DBackpropFilterV2 function. This can result in system crashes or unresponsiveness.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. It analyzes your Pipfile.lock and provides real-time alerts for open-source vulnerabilities, including CVE-2022-29196.

No, not all versions of TensorFlow are affected. The vulnerability exists in TensorFlow versions 2.6.0 to 2.6.3, 2.7.0 to 2.7.1, and 2.8.0. The issue has been fixed in TensorFlow 2.6.4, 2.7.2, 2.8.1, and will be included in the upcoming TensorFlow 2.9.0 release.

Yes, the CVSS score for this vulnerability is 5.5, indicating a moderate severity level.

For more information regarding TensorFlow security, including how to report issues and contact the TensorFlow team, please refer to the security guide in the TensorFlow GitHub repository: https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md

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