CVE-2021-41211: TensorFlow Heap Out-of-Bounds Read in QuantizeV2

tensorflow-cpu Updated 02 Oct 2025

Summary

05/11/2021
Yes i
Unrated
Not published

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

>= 2.6.0, < 2.6.1 >= 2.7.0rc0, < 2.7.0 < a0d64445116c43cf46a5666bd4eee28e7a82f244

Fixed in 2.6.1 or 2.7.0, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2021-41211 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 allows users to build and train neural networks, perform data preprocessing and augmentation, and deploy models in various environments. It is widely used in both research and production settings for a wide range of machine learning tasks.

Vulnerability Detail

The vulnerability identified as CVE-2021-41211 affects TensorFlow versions 2.6.0 to 2.6.1 and 2.7.0rc0 to 2.7.0. The issue lies in the shape inference code for the QuantizeV2 operation. When the axis parameter is a negative value less than -1, the code can trigger a read outside the bounds of a heap-allocated array. This results in a heap out-of-bounds read, accessing data before the start of a heap buffer. The code assumes that axis is a valid index into the dimensions of the input tensor, but if it is less than -1, the vulnerability occurs. The impact of this vulnerability can vary depending on the specific usage scenario, but it could potentially lead to information disclosure or denial of service.

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.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

There is no specific workaround provided for this vulnerability. The recommended course of action is to update to the fixed versions of TensorFlow as soon as they are released.

Conclusion

The vulnerability identified as CVE-2021-41211 in TensorFlow can result in a heap out-of-bounds read when the axis parameter is a negative value less than -1. This can potentially lead to information disclosure or denial of service. Users are advised to update their TensorFlow installations to the fixed versions (2.6.1 or 2.7.0) as soon as they become available. Regularly monitoring for security advisories and following best practices for secure software development and deployment is also recommended. 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 affects TensorFlow versions 2.6.0 to 2.6.1 and 2.7.0rc0 to 2.7.0.

The impact can vary depending on the specific usage scenario, but it could potentially lead to information disclosure or denial of service.

The fix will be included in TensorFlow 2.7.0 and cherrypicked for TensorFlow 2.6.1. Users should update their installations to the fixed versions.

No specific workarounds are provided. Updating to the fixed versions is the recommended action.

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.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