CVE-2022-41911 json
Invalid char to bool conversion when printing a tensor in Tensorflow
published 2022-11-18 3 y ago modified 2026-09-08 2 mo ago also BIT-tensorflow-2022-41911 , EUVD-2022-7399 , GHSA-pf36-r9c6-h97j , PYSEC-2026-1954 , PYSEC-2026-3222 , PYSEC-2026-939
- cvss
- 4.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- public exploits
- 0
- none known
Summary
TensorFlow is an open source platform for machine learning. When printing a tensor, we get it's data as a `const char*` array (since that's the underlying storage) and then we typecast it to the element type. However, conversions from `char` to `bool` are undefined if the `char` is not `0` or `1`, so sanitizers/fuzzers will crash. The issue has been patched in GitHub commit `1be74370327`. The fix will be included in TensorFlow 2.11.0. We will also cherrypick this commit on TensorFlow 2.10.1, TensorFlow 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range.
Patch / fix
- pypi tensorflow 2.8.4, 2.9.3, 2.10.1
- pypi tensorflow-cpu 2.8.4, 2.9.3, 2.10.1
- pypi tensorflow-gpu 2.8.4, 2.9.3, 2.10.1
- bitnami tensorflow 2.8.4, 2.9.3, 2.10.1
- google tensorflow 2.8.4, 2.9.3
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/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 | 4.8 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | tensorflow | <2.8.4 >=2.9.0, <2.9.3 >=2.10.0, <2.10.1 |
2.8.4 2.9.3 2.10.1 |
| pypi | tensorflow-cpu | >=2.9.0, <2.9.3 <2.8.4 >=2.10.0, <2.10.1 |
2.9.3 2.8.4 2.10.1 |
| pypi | tensorflow-gpu | >=2.10.0, <2.10.1 <2.8.4 >=2.9.0, <2.9.3 |
2.10.1 2.8.4 2.9.3 |
| bitnami | tensorflow | <2.8.4 >=2.9.0, <2.9.3 >=2.10.0, <2.10.1 |
2.8.4 2.9.3 2.10.1 |
Affected products
- tensorflow tensorflow
Classification
- Weakness
-
- CWE-704 Incorrect Type Conversion or Cast
References
-
github.com
/tensorflow/tensorflow/commit/1be743703279782a357adbf9b77dcb994fe8b508
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/security/advisories/GHSA-pf36-r9c6-h97j
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/blob/807cae8a807960fd7ac2313cde73a11fc15e7942/tensorflow/core/framework/tensor.cc#L1200
web, patch, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-41911
advisory, web
-
github.com
/tensorflow/tensorflow
package
-
pypi.org
/project/tensorflow-cpu
package
-
github.com
/advisories/GHSA-pf36-r9c6-h97j
advisory
-
pypi.org
/project/tensorflow
package
Sources
- CVE List CVE-2022-41911
- GitHub Advisory GHSA-pf36-r9c6-h97j
- NVD CVE-2022-41911
- OSV BIT-tensorflow-2022-41911
- OSV PYSEC-2026-1954
- OSV PYSEC-2026-3222
- OSV PYSEC-2026-939
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.