PyPI: tensorflow-gpu

CVE-2020-15196

Safety vulnerability ID: SFTY-20200925-73465

Safety legacy ID: pyup.io-56336

Tensorflow-gpu version 2.3.1 includes a fix for CVE-2020-15196: In Tensorflow version 2.3.0, the "SparseCountSparseOutput" and "RaggedCountSparseOutput" implementations don't validate that the "weights" tensor has the same shape as the data. The check exists for "DenseCountSparseOutput", where both tensors are fully specified. In the sparse and ragged count weights are still accessed in parallel with the data. But, since there is no validation, a user passing fewer weights than the values for the tensors can generate a read from outside the bounds of the heap buffer allocated for the weights. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02. https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pg59-2f92-5cph

Created at: Jul 5, 2026Updated at: Jul 5, 2026

Overview

Heap buffer overflow in Tensorflow

Advisory

Tensorflow-gpu version 2.3.1 includes a fix for CVE-2020-15196: In Tensorflow version 2.3.0, the "SparseCountSparseOutput" and "RaggedCountSparseOutput" implementations don't validate that the "weights" tensor has the same shape as the data. The check exists for "DenseCountSparseOutput", where both tensors are fully specified. In the sparse and ragged count weights are still accessed in parallel with the data. But, since there is no validation, a user passing fewer weights than the values for the tensors can generate a read from outside the bounds of the heap buffer allocated for the weights. The issue was patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02. https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pg59-2f92-5cph

Affected Package

Affecting tensorflow-gpu package, versions>=2.3.0rc0,<2.3.1

Also affects

---

How to Fix

Upgradetensorflow-gputo2.3.1or higher.

Mitigation and Workarounds

---

Vulnerable Functions

Functions linked to known vulnerabilities.

Vulnerable function data is available for Enterprise customers

Book a call with us to see Safety in action.

Safety

Verified by Safety

Our Cybersecurity Intelligence Team reviewed this vulnerability. We combine public data with our own research to find issues not yet reported to public sources.

Learn more