LiveActive security incident?Get immediate response
CVE Record

CVE-2021-37655: Heap OOB in `ResourceScatterUpdate` in TensorFlow

TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a read from outside of bounds of heap allocated data by sending invalid arguments to `tf.raw_ops.ResourceScatterUpdate`. The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L919-L923) has an incomplete validation of the relationship between the shapes of `indices` and `updates`: instead of checking that the shape of `indices` is a prefix of the shape of `updates` (so that broadcasting can happen), code only checks that the number of elements in these two tensors are in a divisibility relationship. We have patched the issue in GitHub commit 01cff3f986259d661103412a20745928c727326f. 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.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-37655 is a TensorFlow memory-safety flaw. Invalid inputs to a low-level tensor update operation can make TensorFlow read outside allocated heap memory, risking data exposure and process disruption in affected installations.

Executive priority

Treat this as a high-priority dependency update for ML environments, especially shared research, notebook, or job-execution platforms. It is not currently evidenced as actively exploited in the provided sources.

Technical view

`tf.raw_ops.ResourceScatterUpdate` validated `indices` and `updates` shape relationships incompletely, checking divisibility rather than requiring `indices` to be a prefix of `updates`. This can trigger a heap out-of-bounds read. TensorFlow patched it in commit 01cff3f986259d661103412a20745928c727326f.

Likely exposure

Exposure is limited to TensorFlow deployments running affected versions: 2.5.0 before 2.5.1, 2.4.x before 2.4.3, or versions before 2.3.4. Risk is highest where untrusted users or workloads can supply TensorFlow operation arguments.

Exploitation context

The CVSS vector indicates local access with low privileges, low complexity, and no user interaction. The provided sources do not show CISA KEV listing or active exploitation evidence, so exploitation in the wild should not be assumed.

Researcher notes

The issue is CWE-125 heap out-of-bounds read in TensorFlow resource variable operations. Avoid assuming remote exploitability unless the deployment lets untrusted actors reach TensorFlow execution paths. Public evidence provided names the fix commit and patched release targets.

Mitigation direction

  • Upgrade TensorFlow to 2.6.0 or later where feasible.
  • Apply fixed supported releases: 2.5.1, 2.4.3, or 2.3.4.
  • Rebuild application images and environments that package vulnerable TensorFlow versions.
  • Restrict untrusted TensorFlow workload submission until patched.
  • Check TensorFlow advisory for branch-specific vendor guidance.

Validation and detection

  • Inventory TensorFlow versions across applications, notebooks, jobs, and containers.
  • Check dependency lockfiles and SBOMs for affected TensorFlow ranges.
  • Confirm runtime environments load patched TensorFlow versions.
  • Identify workflows where untrusted users can invoke TensorFlow operations.
  • Document patch status and remaining unsupported TensorFlow deployments.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-125: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-37655 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H1.85.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2021-37655Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
tensorflowtensorflow>= 2.5.0, < 2.5.1, >= 2.4.0, < 2.4.3, < 2.3.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.