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

tensorflow Updated 02 Oct 2025

Summary

06/03/2024
Yes i
Medium
Not published

CVE-2022-23582: CHECK-failures in TensorByteSize 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-23582 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 of tools, libraries, and resources 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 to 2.6.2 and 2.7.0 of TensorFlow.

Vulnerability Detail

A malicious user can exploit this vulnerability by manipulating a SavedModel in a way that triggers CHECK failures related to TensorByteSize. The TensorShape constructor in TensorFlow throws a CHECK-fail if the shape is partial or exceeds the size of an int. However, the PartialTensorShape constructor does not cause a CHECK-abort if the shape is partial, which is necessary for the function to return -1. This vulnerability can lead to a denial of service, impacting the availability of TensorFlow applications.

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

There is no known workaround available for this vulnerability at the moment.

Conclusion

The vulnerability in TensorFlow can be mitigated by updating to the fixed versions. Users are advised to upgrade their installations to TensorFlow 2.6.3, 2.7.1, or wait for the upcoming TensorFlow 2.8.0 release. 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 machine learning framework developed by Google. It provides tools and resources for building and deploying machine learning models.

This vulnerability can lead to a denial of service, affecting the availability of TensorFlow applications.

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

To fix this vulnerability, users should update their TensorFlow installations to the fixed versions, such as TensorFlow 2.6.3, 2.7.1, or the upcoming TensorFlow 2.8.0 release.

There is currently no known workaround for this vulnerability.

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