CVE-2022-23564: Reachable Assertion in TensorFlow
Summary
CVE-2022-23564: Reachable Assertion 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
- tensorflow · Bitnami
- tensorflow-gpu · PyPI
- tensorflow-cpu · PyPI
The same CVE-2022-23564 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
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.
No signup required · Results in about 60 seconds
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 can lead to denial of service attacks.
Vulnerability Detail
The vulnerability in TensorFlow arises when decoding a resource handle tensor from protobuf. In certain cases, a CHECK assertion can be invalidated based on user-controlled arguments. This allows attackers to exploit the vulnerability and cause denial of service in TensorFlow processes. The impact of this vulnerability can disrupt the availability of TensorFlow applications and potentially affect the overall system performance.
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.5.32.5.3pip install --upgrade "tensorflow==2.5.3" -
>= 2.6.0, < 2.6.32.6.3pip install --upgrade "tensorflow==2.6.3" -
>= 2.7.0, < 2.7.12.7.1pip install --upgrade "tensorflow==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 specific workaround provided for this vulnerability. The recommended solution is to apply the patches or upgrade to the fixed versions of TensorFlow.
Conclusion
The vulnerability in TensorFlow can lead to denial of service attacks and impact the availability and performance of TensorFlow applications. It is crucial to apply the patches or upgrade to the fixed versions to mitigate the risk. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for tensorflow →
FAQ
The vulnerability can be exploited to cause denial of service in TensorFlow processes, leading to application unavailability and potential system performance issues.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your TensorFlow installation is affected by this vulnerability. It provides real-time monitoring and alerts for open-source vulnerabilities without requiring access to the code or installation.
No, not all versions of TensorFlow are affected. The vulnerability exists in TensorFlow versions 2.5.3, 2.6.3, 2.7.1, and earlier. It has been fixed in TensorFlow 2.8.0 and backported to the aforementioned versions.
There is no known public exploit for this vulnerability at the time of this advisory. However, it is recommended to apply the patches or upgrade to the fixed versions to mitigate the risk.
You can refer to the TensorFlow security guide (https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact the TensorFlow team with any security issues or questions.
References
Related vulnerabilities
Recent vulnerabilities recorded for tensorflow.
