CVE-2022-23581: TensorFlow - Denial of Service Vulnerability

tensorflow Updated 02 Oct 2025

Summary

06/03/2024
Yes i
Medium
Not published

CVE-2022-23581: CHECK-failures during Grappler's IsSimplifiableReshape in Tensorflow. Affects tensorflow across 3 version ranges.

< 2.5.3 >= 2.6.0, < 2.6.3 >= 2.7.0, < 2.7.1

Fixed in 2.5.3, 2.6.3 or 2.7.1, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2022-23581 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 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 developed by Google. It provides a comprehensive ecosystem for building and deploying machine learning models. TensorFlow is widely used in various domains, including research, industry, and academia. This vulnerability affects versions 2.5.2, 2.6.0, and 2.6.2 of TensorFlow, as well as version 2.7.0. The Grappler optimizer in TensorFlow is susceptible to a denial of service attack due to a flaw in the handling of SavedModel. By manipulating a SavedModel to trigger CHECK failures in the IsSimplifiableReshape function, an attacker can cause the TensorFlow application to crash, resulting in a denial of service.

Vulnerability Detail

The vulnerability in TensorFlow arises from a weakness in the Grappler optimizer's handling of SavedModel. When a SavedModel is altered in a specific way, the IsSimplifiableReshape function can be triggered to encounter CHECK failures. This can lead to the TensorFlow application crashing, rendering it unavailable. The impact of this vulnerability is a denial of service, which can disrupt critical machine learning processes and potentially impact the availability of services relying on TensorFlow. The vulnerability has been assigned the identifier CVE-2022-23581.

How To Fix

Fixed versions by release line

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

  • < 2.5.3 2.5.3
  • >= 2.6.0, < 2.6.3 2.6.3
  • >= 2.7.0, < 2.7.1 2.7.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

No workaround has been provided for this vulnerability. It is essential to update TensorFlow to the patched version to ensure the security and stability of the application.

Conclusion

The vulnerability in TensorFlow can lead to a denial of service attack by crashing the application. To mitigate this risk, it is essential to update TensorFlow to the latest patched version. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for tensorflow →

Share this vulnerability

FAQ

TensorFlow is an open-source machine learning framework developed by Google. It provides a comprehensive ecosystem for building and deploying machine learning models.

The vulnerability allows an attacker to cause a denial of service by crashing the TensorFlow application, potentially disrupting critical machine learning processes and impacting the availability of services relying on TensorFlow.

Versions 2.5.2, 2.6.0, 2.6.2, and 2.7.0 of TensorFlow are affected by this vulnerability.

To fix this vulnerability, it is recommended to update TensorFlow to version 2.8.0. The fix will also be backported to versions 2.7.1, 2.6.3, and 2.5.3.

No workaround has been provided for this vulnerability. It is crucial to update TensorFlow to the patched version.

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.5.3 2.5.3
  • >= 2.6.0, < 2.6.3 2.6.3
  • >= 2.7.0, < 2.7.1 2.7.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