CVE-2021-41211 is a high-severity (CVSS 7.1) Out-of-bounds Read vulnerability in tensorflow. 1 public exploit reference exists, so weaponization risk is real. A fix is available for tensorflow — see the affected versions and patch details below.
Heap OOB in shape inference for `QuantizeV2`
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2021-41211 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
tensorflow🐍tensorflow-cpu🐍tensorflow-gpuReal-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 code for QuantizeV2 can trigger a read outside of bounds of heap allocated array:
import tensorflow as tf
@tf.function
def test():
data=tf.raw_ops.QuantizeV2(
input=[1.0,1.0],
min_range=[1.0,10.0],
max_range=[1.0,10.0],
T=tf.qint32,
mode='MIN_COMBINED',
round_mode='HALF_TO_EVEN',
narrow_range=False,
axis=-100,
ensure_minimum_range=10)
return data
test()
This occurs whenever axis is a negative value less than -1. In this case, we are accessing data before the start of a heap buffer:
int axis = -1;
Status s = c->GetAttr("axis", &axis);
if (!s.ok() && s.code() != error::NOT_FOUND) {
return s;
}
...
if (axis != -1) {
...
TF_RETURN_IF_ERROR(
c->Merge(c->Dim(minmax, 0), c->Dim(input, axis), &depth));
}
The code allows axis to be an optional argument (s would contain an error::NOT_FOUND error code). Otherwise, it assumes that axis is a valid index into the dimensions of the input tensor. If axis is less than -1 then this results in a heap OOB read.
Patches
We have patched the issue in GitHub commit a0d64445116c43cf46a5666bd4eee28e7a82f244.
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, as this version is the only one that is also affected.
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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | tensorflow | ≥ 2.6.0&&< 2.6.1 | 2.6.1pip install --upgrade 'tensorflow==2.6.1' |
| 🐍PyPI | tensorflow-cpu | ≥ 2.6.0&&< 2.6.1 | 2.6.1pip install --upgrade 'tensorflow-cpu==2.6.1' |
| 🐍PyPI | tensorflow-gpu | ≥ 2.6.0&&< 2.6.1 | 2.6.1pip install --upgrade 'tensorflow-gpu==2.6.1' |
Affected Products
tensorflowgoogleResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
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.
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-41211 is resolved across your whole dependency graph.
Workarounds
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.
Frequently Asked Questions
Is CVE-2021-41211 in your dependencies?
Find it across PyPI, including transitive dependencies.