Out of bounds read in Tensorflow
Impact
TensorFlow's type inference can cause a heap OOB read as the bounds checking is done in a DCHECK (which is a no-op during production):
if (node_t.type_id() != TFT_UNSET) {
int ix = input_idx[i];
DCHECK(ix < node_t.args_size())
<< "input " << i << " should have an output " << ix
<< " but instead only has " << node_t.args_size()
<< " outputs: " << node_t.DebugString();
input_types.emplace_back(node_t.args(ix));
// ...
}
An attacker can control input_idx such that ix would be larger than the number of values in node_t.args.
Patches
We have patched the issue in GitHub commit c99d98cd189839dcf51aee94e7437b54b31f8abd.
The fix will be included in TensorFlow 2.8.0. This is the only affected version.
For more information
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Python (PyPI) | tensorflow | >= 2.8.0-rc0, < 2.8.0 | 2.8.0 |
| Python (PyPI) | tensorflow-cpu | >= 2.7.0, < 2.8.0 | 2.8.0 |
| Python (PyPI) | tensorflow-gpu | >= 2.7.0, < 2.8.0 | 2.8.0 |
References
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-vq36-27g6-p492
- https://nvd.nist.gov/vuln/detail/CVE-2022-23592
- https://github.com/tensorflow/tensorflow/commit/c99d98cd189839dcf51aee94e7437b54b31f8abd
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2022-101.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2022-156.yaml
- https://github.com/tensorflow/tensorflow
- https://github.com/tensorflow/tensorflow/blob/274df9b02330b790aa8de1cee164b70f72b9b244/tensorflow/core/graph/graph.cc#L223-L229
- https://pypi.org/project/tensorflow
- https://github.com/advisories/GHSA-vq36-27g6-p492
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H- Weakness (CWE)
CWE-125- Platform
- Python (PyPI)
- Package
tensorflow, tensorflow-cpu, tensorflow-gpu- Disclosed
- 04.02.2022
- Updated
- 11.10.2026 14:18
Sources and licenses
OSV / GitHub Advisory Database - PYSEC-2022-101 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2022-156 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-vq36-27g6-p492 - CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2026-3249 - PyPA Advisory Database; CC BY 4.0
Vulnerability history: tensorflow
All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 433
- First → latest
- 04.2019 07.2024
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 6
- High 112
- Medium 210
- Low 105
Disclosures per year
- 2019: 7
- 2020: 35
- 2021: 200
- 2022: 169
- 2023: 21
- 2024: 1
- 2025: 0
- 2026: 0
-
Out of bounds read in Tensorflow this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.