Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

CVE-2021-41216 — tensorflow

HIGHFix: tensorflow/tensorflow@c79ba87

CVE-2021-41216 is a high-severity (CVSS 7.8) CWE-120 vulnerability in tensorflow. A fix is available for tensorflow — see the affected versions and patch details below.

Heap buffer overflow in `Transpose`

Also known asBIT-tensorflow-2021-41216GHSA-3ff2-r28g-w7h9PYSEC-2021-408PYSEC-2021-625PYSEC-2021-823
Published
Updated
Affected
9 pkgs
Patched
9 / 9
Exploits
None indexed
Exploitation data as of Oct 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs5th percentile — riskier than 5% of all scored CVEsHighest risk
0.00%0.22%0.44%0.66%0.2%0.2%0.2%Jul 26Oct 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-41216 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

9 pkgs affected
🐍tensorflow🐍tensorflow🐍tensorflow🐍tensorflow-cpu🐍tensorflow-cpu🐍tensorflow-cpu🐍tensorflow-gpu🐍tensorflow-gpu+1 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The shape inference function for Transpose is vulnerable to a heap buffer overflow:

import tensorflow as tf
@tf.function
def test():
  y = tf.raw_ops.Transpose(x=[1,2,3,4],perm=[-10])
  return y

test()

This occurs whenever perm contains negative elements. The shape inference function does not validate that the indices in perm are all valid:

for (int32_t i = 0; i < rank; ++i) {
  int64_t in_idx = data[i];
  if (in_idx >= rank) {
    return errors::InvalidArgument("perm dim ", in_idx,
                                   " is out of range of input rank ", rank);
  }
  dims[i] = c->Dim(input, in_idx);
}

where Dim(tensor, index) accepts either a positive index less than the rank of the tensor or the special value -1 for unknown dimensions.

Patches

We have patched the issue in GitHub commit c79ba87153ee343401dbe9d1954d7f79e521eb14.

The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.

For more information

Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Attribution

This vulnerability has been reported by members of the Aivul Team from Qihoo 360.

Affected Packages

9 total 9 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPItensorflow≥ 2.6.0&&< 2.6.12.6.1pip install --upgrade 'tensorflow==2.6.1'
🐍PyPItensorflow≥ 2.5.0&&< 2.5.22.5.2pip install --upgrade 'tensorflow==2.5.2'
🐍PyPItensorflowall versions2.4.4pip install --upgrade 'tensorflow==2.4.4'
🐍PyPItensorflow-cpu≥ 2.6.0&&< 2.6.12.6.1pip install --upgrade 'tensorflow-cpu==2.6.1'
🐍PyPItensorflow-cpu≥ 2.5.0&&< 2.5.22.5.2pip install --upgrade 'tensorflow-cpu==2.5.2'
🐍PyPItensorflow-cpuall versions2.4.4pip install --upgrade 'tensorflow-cpu==2.4.4'

Affected Products

1 product · 5 configurations
Application
tensorflowgoogle
≥ 2.6.0 && < 2.6.1
1 version
2.7.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tensorflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update tensorflow to 2.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-41216 is resolved across your whole dependency graph.

  3. Workarounds

    Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

### Impact The [shape inference function for `Transpose`](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/ops/array_ops.cc#L121-L185) is vulnerable to a heap buffer overflow: ```python import tensorflow as tf @tf.function def test(): y = tf.raw_ops.Transpose(x=[1,2,3,4],perm=[-10]) return y test() ``` This occurs whenever `perm` contains negative elements. The shape inference function does not validate that the indices in `perm` are all valid: ```cc for (int32_t i = 0; i < rank; ++i) { int64_t in_idx = data[i]; if (in_i
O3 Security · Impact-Aware SCA

Is CVE-2021-41216 in your dependencies?

Find it across PyPI, including transitive dependencies.

CVE-2021-41216: tensorflow — Fixed in 2.6.1