CVE-2021-37641

Heap OOB in `RaggedGather` in TensorFlow

HIGH
7.1
CVSS Score
Published: August 12, 2021 at 08:30 PM UTC
Updated: June 17, 2026 at 04:00 AM UTC
2 products affected across 2 vendorsTensorflowTensorFlow

Using tensorflow by tensorflow?

Get instant alerts when new vulnerabilities affect tensorflow - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.1
Exploit prediction
EPSS 0.2%

Description

TensorFlow is an end-to-end open source platform for machine learning. In affected versions if the arguments to `tf.raw_ops.RaggedGather` don't determine a valid ragged tensor code can trigger a read from outside of bounds of heap allocated buffers. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/ragged_gather_op.cc#L70) directly reads the first dimension of a tensor shape before checking that said tensor has rank of at least 1 (i.e., it is not a scalar). Furthermore, the implementation does not check that the list given by `params_nested_splits` is not an empty list of tensors. We have patched the issue in GitHub commit a2b743f6017d7b97af1fe49087ae15f0ac634373. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.3.0 ≤ v < 2.3.42.4.0 ≤ v < 2.4.32.5.02.6.0 rc02.6.0 rc12.6.0 rc2
Affected range stops below 2.3.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.4.3, so it looks safe — our inference, not a vendor statement
v < 2.3.4v < 2.4.3v < 2.5.1
Affected range stops below 2.3.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.4.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.5.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-125

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card