CVE-2021-41200: TensorFlow - Non-scalar Arguments Crash

tensorflow-cpu Updated 02 Oct 2025

Summary

05/11/2021
Yes i
Unrated
Not published

CVE-2021-41200: TensorFlow is an open source platform for machine learning. Affects tensorflow-cpu across 5 version ranges.

< 2.4.4 >= 2.5.0, < 2.5.2 >= 2.6.0, < 2.6.1 >= 2.7.0rc0, < 2.7.0 < 874bda09e6702cd50bac90b453b50bcc65b2769e

Fixed in 4 releases; the minimum fixed version depends on the release line you run. How to fix ↓

Also tracked for

The same CVE-2021-41200 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

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. It offers extensive support for deep learning algorithms and enables efficient computation on both CPUs and GPUs. However, a vulnerability has been identified in TensorFlow that can lead to a crash when certain non-scalar arguments are passed to the tf.summary.create_file_writer function.

Vulnerability Detail

The vulnerability (CVE-2021-41200) in TensorFlow arises when the tf.summary.create_file_writer function is called with non-scalar arguments. This triggers a CHECK-fail, causing the code to crash. The vulnerability can be exploited by an attacker to disrupt the execution of TensorFlow-based applications or potentially cause a denial-of-service (DoS) condition. The impact of this vulnerability depends on the context in which TensorFlow is used and the availability of mitigations. It is important to note that this vulnerability affects multiple versions of TensorFlow, including 2.4.4, 2.5.2, 2.6.1, and 2.7.0rc0.

How To Fix

Latest published version: 2.21.0 as of 22 Oct 2026

pip install --upgrade "tensorflow-cpu==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.4.4 2.4.4
    pip install --upgrade "tensorflow-cpu==2.4.4"
  • >= 2.5.0, < 2.5.2 2.5.2
    pip install --upgrade "tensorflow-cpu==2.5.2"
  • >= 2.6.0, < 2.6.1 2.6.1
    pip install --upgrade "tensorflow-cpu==2.6.1"
  • >= 2.7.0rc0, < 2.7.0 2.7.0
    pip install --upgrade "tensorflow-cpu==2.7.0"

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, users can avoid passing non-scalar arguments to the tf.summary.create_file_writer function. Instead, ensure that only scalar arguments are used when creating the file writer. Here is an example of how to create a file writer with scalar arguments:

import tensorflow as tf

with tf.summary.create_file_writer('logs').as_default():
    # Your code here

By following this workaround, the vulnerability can be mitigated until the updated versions of TensorFlow are installed.

Conclusion

The vulnerability in TensorFlow (CVE-2021-41200) can lead to a crash in TensorFlow-based applications when non-scalar arguments are passed to the tf.summary.create_file_writer function. It is crucial to update TensorFlow installations to the fixed versions (2.7.0, 2.6.1, 2.5.2, or 2.4.4) to mitigate this vulnerability. In the meantime, users can follow the provided workaround to avoid the vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for tensorflow-cpu →

Share this vulnerability

FAQ

TensorFlow is an open source platform for machine learning that provides tools and libraries for developing and deploying machine learning models.

The vulnerability can lead to a crash in TensorFlow-based applications when non-scalar arguments are passed to the tf.summary.create_file_writer function. This can potentially disrupt the execution of the application or cause a denial-of-service (DoS) condition.

The vulnerability affects TensorFlow versions 2.4.4, 2.5.2, 2.6.1, and 2.7.0rc0.

To fix the vulnerability, users should update their TensorFlow installations to the fixed versions (2.7.0, 2.6.1, 2.5.2, or 2.4.4). This can be done by upgrading the TensorFlow package using the package manager or by manually installing the updated version from the official TensorFlow repository.

Yes, a workaround is available. Users can avoid passing non-scalar arguments to the tf.summary.create_file_writer function and ensure that only scalar arguments are used when creating the file writer.

Related vulnerabilities

Recent vulnerabilities recorded for tensorflow-cpu.

How To Fix

Latest published version: 2.21.0 as of 22 Oct 2026

pip install --upgrade "tensorflow-cpu==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.4.4 2.4.4
    pip install --upgrade "tensorflow-cpu==2.4.4"
  • >= 2.5.0, < 2.5.2 2.5.2
    pip install --upgrade "tensorflow-cpu==2.5.2"
  • >= 2.6.0, < 2.6.1 2.6.1
    pip install --upgrade "tensorflow-cpu==2.6.1"
  • >= 2.7.0rc0, < 2.7.0 2.7.0
    pip install --upgrade "tensorflow-cpu==2.7.0"

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