CVE-2022-35969: TensorFlow GPU Vulnerable to CHECK Fail in Conv2DBackpropInput

tensorflow-gpu Updated 07 Jul 2026

Summary

07/07/2026
Yes i
Medium
5.9

CVE-2022-35969: TensorFlow vulnerable to CHECK fail in Conv2DBackpropInput. Affects tensorflow-gpu across 3 version ranges.

< 2.7.2 >= 2.8.0, < 2.8.1 >= 2.9.0, < 2.9.1

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

Also tracked for

The same CVE-2022-35969 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

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

TensorFlow is an open-source machine learning framework widely used for building and training deep learning models. It provides a comprehensive ecosystem for developing and deploying machine learning applications. The framework includes various operations, including convolutional layers, which are essential for processing image data. However, a vulnerability has been identified in the Conv2DBackpropInput operation, which can lead to denial of service under specific conditions.

Vulnerability Detail

The vulnerability arises from the Conv2DBackpropInput operation requiring input_sizes to be a 4-dimensional tensor. If this requirement is not met, it triggers a CHECK failure, which can be exploited to cause a denial of service. This means that an attacker could potentially crash the application by providing malformed input sizes, leading to unexpected behavior and service interruptions. The vulnerability has been assigned a CVSS score of 5.9, indicating a moderate severity level.

How To Fix

Latest published version: 2.12.0 as of 22 Oct 2026

pip install --upgrade "tensorflow-gpu==2.12.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.7.2 2.7.2
    pip install --upgrade "tensorflow-gpu==2.7.2"
  • >= 2.8.0, < 2.8.1 2.8.1
    pip install --upgrade "tensorflow-gpu==2.8.1"
  • >= 2.9.0, < 2.9.1 2.9.1
    pip install --upgrade "tensorflow-gpu==2.9.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, ensure that the input_sizes parameter passed to the Conv2DBackpropInput operation is always a 4-dimensional tensor. For example, you can modify your code as follows:

import tensorflow as tf

strides = [1, 1, 1, 1] padding = 'SAME' use_cudnn_on_gpu = True explicit_paddings = [] dilations = [1, 1, 1, 1] input_sizes = tf.constant([1, 64, 64, 2], shape=[4], dtype=tf.int32) # Ensure this is 4D filter = tf.constant(0.159749106, shape=[3, 3, 2, 2], dtype=tf.float32) out_backprop = tf.constant(0, shape=[], dtype=tf.float32) tf.raw_ops.Conv2DBackpropInput(input_sizes=input_sizes, filter=filter, out_backprop=out_backprop, strides=strides, padding=padding, use_cudnn_on_gpu=use_cudnn_on_gpu, explicit_paddings=explicit_paddings, data_format='NHWC', dilations=dilations)

Conclusion

The vulnerability CVE-2022-35969 in TensorFlow's Conv2DBackpropInput operation poses a risk of denial of service due to improper input size handling. It is crucial for users to update to the patched versions or implement workarounds to mitigate the risk. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for tensorflow-gpu →

Share this vulnerability

FAQ

CVE-2022-35969 is a vulnerability in TensorFlow's Conv2DBackpropInput operation that can lead to a denial of service due to a CHECK failure when input sizes are not 4-dimensional.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

The vulnerability has a CVSS score of 5.9, indicating a moderate severity level.

The affected versions include TensorFlow 2.7.0, 2.8.0, and 2.9.0. The vulnerability has been fixed in versions 2.7.2, 2.8.1, and 2.9.1.

If you cannot update TensorFlow, ensure that you validate the input sizes to the Conv2DBackpropInput operation to be 4-dimensional to avoid triggering the vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for tensorflow-gpu.

How To Fix

Latest published version: 2.12.0 as of 22 Oct 2026

pip install --upgrade "tensorflow-gpu==2.12.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.7.2 2.7.2
    pip install --upgrade "tensorflow-gpu==2.7.2"
  • >= 2.8.0, < 2.8.1 2.8.1
    pip install --upgrade "tensorflow-gpu==2.8.1"
  • >= 2.9.0, < 2.9.1 2.9.1
    pip install --upgrade "tensorflow-gpu==2.9.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