Skip to content
Fencer Vulns
medium 5.9

CVE-2022-35998 json

`CHECK` fail in `EmptyTensorList` in TensorFlow

published 2022-09-16 4 y ago modified 2026-09-08 2 mo ago also BIT-tensorflow-2022-35998 , EUVD-2022-6918 , GHSA-qhw4-wwr7-gjc5 , PYSEC-2026-937

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 42%
public exploits
0
none known

Summary

TensorFlow is an open source platform for machine learning. If `EmptyTensorList` receives an input `element_shape` with more than one dimension, it gives a `CHECK` fail that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit c8ba76d48567aed347508e0552a257641931024d. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue.

Patch / fix

  • pypi tensorflow 2.7.2, 2.8.1, 2.9.1
  • bitnami tensorflow 2.7.2, 2.8.1, 2.9.1
  • google tensorflow 2.7.2, 2.8.1, 2.9.1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
pypi tensorflow
<2.7.2
>=2.8.0, <2.8.1
>=2.9.0, <2.9.1
2.7.2
2.8.1
2.9.1
bitnami tensorflow
<2.7.2
>=2.8.0, <2.8.1
>=2.9.0, <2.9.1
2.7.2
2.8.1
2.9.1

Affected products

  • tensorflow tensorflow

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.