CVE-2022-35935 json
`CHECK` failure in `SobolSample` via missing validation in TensorFlow
published 2022-09-16 4 y ago modified 2026-09-08 2 mo ago also BIT-tensorflow-2022-35935 , EUVD-2022-6752 , GHSA-97p7-w86h-vcf9 , PYSEC-2026-3144 , PYSEC-2026-3302 , PYSEC-2026-974
- 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 45%
- public exploits
- 0
- none known
Summary
TensorFlow is an open source platform for machine learning. The implementation of SobolSampleOp is vulnerable to a denial of service via CHECK-failure (assertion failure) caused by assuming `input(0)`, `input(1)`, and `input(2)` to be scalar. This issue has been patched in GitHub commit c65c67f88ad770662e8f191269a907bf2b94b1bf. 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
- pypi tensorflow-cpu 2.7.2, 2.8.1, 2.9.1
- pypi tensorflow-gpu 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.53% chance of exploitation in the next 30 days, higher than 45% 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 |
| pypi | tensorflow-cpu | <2.7.2 >=2.8.0, <2.8.1 >=2.9.0, <2.9.1 |
2.7.2 2.8.1 2.9.1 |
| pypi | tensorflow-gpu | <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.0, <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
-
- CWE-617 Reachable Assertion
References
-
github.com
/tensorflow/tensorflow/commit/c65c67f88ad770662e8f191269a907bf2b94b1bf
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/security/advisories/GHSA-97p7-w86h-vcf9
web, patch, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-35935
advisory, web
-
github.com
/tensorflow/tensorflow
package
-
github.com
/tensorflow/tensorflow/releases/tag/v2.10.0
web
-
pypi.org
/project/tensorflow
package
-
github.com
/advisories/GHSA-97p7-w86h-vcf9
advisory
-
pypi.org
/project/tensorflow-cpu
package
-
pypi.org
/project/tensorflow-gpu
package
Sources
- CVE List CVE-2022-35935
- GitHub Advisory GHSA-97p7-w86h-vcf9
- NVD CVE-2022-35935
- OSV BIT-tensorflow-2022-35935
- OSV PYSEC-2026-3144
- OSV PYSEC-2026-3302
- OSV PYSEC-2026-974
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.