CVE-2022-29201 json
Missing validation in `QuantizedConv2D` results in undefined behavior in TensorFlow
published 2022-05-20 4 y ago modified 2026-09-08 2 mo ago also BIT-tensorflow-2022-29201 , EUVD-2022-4806 , GHSA-pqhm-4wvf-2jg8 , PYSEC-2026-1026 , PYSEC-2026-3224 , PYSEC-2026-3358
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.raw_ops.QuantizedConv2D` does not fully validate the input arguments. In this case, references get bound to `nullptr` for each argument that is empty. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.
Patch / fix
- pypi tensorflow 2.6.4, 2.7.2, 2.8.1
- pypi tensorflow-cpu 2.6.4, 2.7.2, 2.8.1
- pypi tensorflow-gpu 2.6.4, 2.7.2, 2.8.1
- bitnami tensorflow 2.6.4, 2.7.2, 2.8.1
- google tensorflow 2.6.4, 2.7.2
- github.com/tensorflow/tensorflow@0f0b080 commit
- github.com/tensorflow/tensorflow/releases/tag/v2.6.4 release
- github.com/tensorflow/tensorflow/releases/tag/v2.7.2 release
- github.com/tensorflow/tensorflow/releases/tag/v2.8.1 release
- github.com/tensorflow/tensorflow/releases/tag/v2.9.0 release
- github.com/tensorflow/tensorflow/security/advisories/GHSA-pqhm-4wvf-2… advisory
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pqhm-4wvf-2jg8 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:N/A:P |
| OSV | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | tensorflow | <2.6.4 >=2.7.0, <2.7.2 >=2.8.0, <2.8.1 |
2.6.4 2.7.2 2.8.1 |
| pypi | tensorflow-cpu | <2.6.4 >=2.7.0, <2.7.2 >=2.8.0, <2.8.1 |
2.6.4 2.7.2 2.8.1 |
| pypi | tensorflow-gpu | <2.6.4 >=2.7.0, <2.7.2 >=2.8.0, <2.8.1 |
2.6.4 2.7.2 2.8.1 |
| bitnami | tensorflow | <2.6.4 >=2.7.0, <2.7.2 >=2.8.0, <2.8.1 |
2.6.4 2.7.2 2.8.1 |
Affected products
- tensorflow tensorflow
Classification
References
-
github.com
/tensorflow/tensorflow/commit/0f0b080ecde4d3dfec158d6f60da34d5e31693c4
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/security/advisories/GHSA-pqhm-4wvf-2jg8
web, exploit, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/releases/tag/v2.6.4
web, release-notes, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/releases/tag/v2.7.2
web, release-notes, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/releases/tag/v2.8.1
web, release-notes, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/releases/tag/v2.9.0
web, release-notes, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/blob/f3b9bf4c3c0597563b289c0512e98d4ce81f886e/tensorflow/core/kernels/quantized_conv_op
web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-29201
advisory, web
-
github.com
/tensorflow/tensorflow
package
-
pypi.org
/project/tensorflow-gpu
package
-
github.com
/advisories/GHSA-pqhm-4wvf-2jg8
advisory
-
pypi.org
/project/tensorflow
package
-
pypi.org
/project/tensorflow-cpu
package
Sources
- CVE List CVE-2022-29201
- GitHub Advisory GHSA-pqhm-4wvf-2jg8
- NVD CVE-2022-29201
- OSV BIT-tensorflow-2022-29201
- OSV PYSEC-2026-1026
- OSV PYSEC-2026-3224
- OSV PYSEC-2026-3358
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.