CVE-2022-41883 json
Out of bounds segmentation fault due to unequal op inputs in Tensorflow
published 3y ago modified 2mo ago also BIT-tensorflow-2022-41883 , EUVD-2022-7448 , GHSA-w58w-79xv-6vcj , PYSEC-2026-1042 , PYSEC-2026-3251 , PYSEC-2026-3376
- cvss
- 6.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 32%
- public exploits
- 0
- none known
Summary
TensorFlow is an open source platform for machine learning. When ops that have specified input sizes receive a differing number of inputs, the executor will crash. We have patched the issue in GitHub commit f5381e0e10b5a61344109c1b7c174c68110f7629. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range.
Patch / fix
- pypi tensorflow 2.10.1
- pypi tensorflow-cpu 2.10.1
- pypi tensorflow-gpu 2.10.1
- bitnami tensorflow 2.10.1
Is CVE-2022-41883 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/tensorflow/tensorflow/security/advisories/GHSA-w58w-79xv-6vcj referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:H |
| GitHub | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/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 | 6.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | tensorflow | >=2.10.0, <2.10.1 |
2.10.1 |
| pypi | tensorflow-cpu | >=2.10.0, <2.10.1 |
2.10.1 |
| pypi | tensorflow-gpu | >=2.10.0, <2.10.1 |
2.10.1 |
| bitnami | tensorflow | >=2.10.0, <2.10.1 |
2.10.1 |
Affected products
- tensorflow tensorflow
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
github.com
/tensorflow/tensorflow/commit/f5381e0e10b5a61344109c1b7c174c68110f7629
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/security/advisories/GHSA-w58w-79xv-6vcj
web, exploit, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/blob/master/tensorflow/core/kernels/dynamic_stitch_op.cc
web, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/blob/master/tensorflow/core/ops/data_flow_ops.cc
web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-41883
advisory, web
-
github.com
/tensorflow/tensorflow
package
-
pypi.org
/project/tensorflow-gpu
package
-
github.com
/advisories/GHSA-w58w-79xv-6vcj
advisory
-
pypi.org
/project/tensorflow
package
-
pypi.org
/project/tensorflow-cpu
package
Sources
- CVE List CVE-2022-41883
- GitHub Advisory GHSA-w58w-79xv-6vcj
- NVD CVE-2022-41883
- OSV BIT-tensorflow-2022-41883
- OSV PYSEC-2026-1042
- OSV PYSEC-2026-3251
- OSV PYSEC-2026-3376
Fencer Intel 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.