CVE-2021-37639: TensorFlow null pointer dereference and heap out-of-bounds read

Summary

TensorFlow's raw tensor restore APIs fail to validate inputs when restoring tensors. If no tensor name is provided, or the list is empty, TensorFlow dereferences a null pointer. If some names are given but too few to satisfy the restoration index, which is controlled by the preferred_shard argument, it performs a heap out-of-bounds read.

Mitigation

We have patched the issue in GitHub commit 9e82dce6e6bd1f36a57e08fa85af213e2b2f2622. The fix will be included in TensorFlow 2.6.0. The commit will also be cherrypicked to TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4.

Affected packages in the Exposure Registry

Matched by package name and ecosystem. Each entry shows whether the package delegates to a language model and how many tracked packages depend on it.

• tensorflowPyPINo LLM dependency detected · 26 tracked dependents
• tensorflow-gpuPyPINo LLM dependency detected · 2 tracked dependents

Related items

• LowCloakFEM: Agentic FEM Code Generation for Red-Teaming Computational Resource ExhaustionSimilar attack · Arxiv (cs.CR + cs.CL + cs.LG)
• MediumThe Rise of LLMJacking: How Threat Actors Monetize Compromised Cloud and Model ResourcesSimilar attack · Google Threat Intelligence
• InfoThe Blind Spots of Detection: Adversarial Perturbation Attacks against Watchdogs in Distributed LLM InferenceSimilar attack · Arxiv (cs.CR + cs.CL + cs.LG)
• HighCVE-2026-118761: Kubeflow Pipelines decompression bomb in pipeline archive uploadSimilar attack · NVD/CVE Database
• LowOpenCode User Hit with Hostile Backlash After Reporting Free AI LoopholeSimilar attack · Socket Blog