CVE-2022-35997: TensorFlow denial of service through tf.sparse.cross with non-scalar separator

Summary

TensorFlow's tf.sparse.cross triggers a CHECK failure when its separator input is not a scalar, which can be used to cause a denial of service. The issue is patched in GitHub commit 83dcb4dbfa094e33db084e97c4d0531a559e0ebf, which is included in TensorFlow 2.10.0 and cherry-picked to TensorFlow 2.9.1, 2.8.1 and 2.7.2, all of which are affected and still in supported range.

Mitigation

Patched in GitHub commit 83dcb4dbfa094e33db084e97c4d0531a559e0ebf, included in TensorFlow 2.10.0 and cherry-picked to TensorFlow 2.9.1, 2.8.1 and 2.7.2. There are no known workarounds for this issue.

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