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

tensorflow Updated 02 Oct 2025

Summary

06/03/2024
Yes i
High
Not published

CVE-2022-35994: CHECK fail in CollectiveGather in TensorFlow. Affects tensorflow 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-35994 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 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. 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-35994, occurs when the CollectiveGather function in TensorFlow receives a scalar input. Due to a flaw in the code, a CHECK fails, allowing an attacker to trigger a denial of service attack. This vulnerability can be exploited by an attacker to disrupt the availability of TensorFlow-based applications or services. The issue has been patched in the GitHub commit c1f491817dec39a26be3c574e86a88c30f3c4770 and will be included in TensorFlow 2.10.0. Additionally, the fix will be backported to TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these versions are also affected and within the supported range.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 2.7.2 2.7.2
  • >= 2.8.0, < 2.8.1 2.8.1
  • >= 2.9.0, < 2.9.1 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 →

Conclusion

In conclusion, the CVE-2022-35994 vulnerability in TensorFlow can lead to a denial of service attack. It is crucial to update TensorFlow to the patched versions or apply the respective patches to ensure the security and stability of machine learning applications. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for tensorflow →

Share this vulnerability

FAQ

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

This vulnerability allows an attacker to trigger a denial of service attack, potentially disrupting the availability of TensorFlow-based applications or services.

To fix this vulnerability, it is recommended to update TensorFlow to version 2.10.0 or apply the respective patches for TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2.

There are no known workarounds for this vulnerability. It is recommended to update TensorFlow to the patched versions.

More information about this vulnerability can be found in the GitHub commit c1f491817dec39a26be3c574e86a88c30f3c4770 and the official TensorFlow documentation.

Related vulnerabilities

Recent vulnerabilities recorded for tensorflow.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 2.7.2 2.7.2
  • >= 2.8.0, < 2.8.1 2.8.1
  • >= 2.9.0, < 2.9.1 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