Medium

TensorFlow vulnerable to `CHECK` failure in `AvgPoolOp`

  • Disclosed: 16.09.2022
  • Updated: 11.10.2026 14:18

Impact

The AvgPoolOp function takes an argument ksize that must be positive but is not checked. A negative ksize can trigger a CHECK failure and crash the program.

python
import tensorflow as tf
import numpy as np

value = np.ones([1, 1, 1, 1])
ksize = [1, 1e20, 1, 1]
strides = [1, 1, 1, 1]
padding = 'SAME'
data_format = 'NHWC'

tf.raw_ops.AvgPool(value=value, ksize=ksize, strides=strides, padding=padding, data_format=data_format)

Patches

We have patched the issue in GitHub commit 3a6ac52664c6c095aa2b114e742b0aa17fdce78f.

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.

For more information

Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Attribution

This vulnerability has been reported by Jingyi Shi.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) tensorflow < 2.7.2, >= 2.8.0, < 2.8.1, >= 2.9.0, < 2.9.2 2.7.2, 2.8.1, 2.9.2
Python (PyPI) tensorflow-cpu < 2.7.2, >= 2.8.0, < 2.8.1, >= 2.9.0, < 2.9.2 2.7.2, 2.8.1, 2.9.2
Python (PyPI) tensorflow-gpu < 2.7.2, >= 2.8.0, < 2.8.1, >= 2.9.0, < 2.9.2 2.7.2, 2.8.1, 2.9.2

References

CVSS score 5.9/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE)
CWE-617
Platform
Python (PyPI)
Package
tensorflow, tensorflow-cpu, tensorflow-gpu
Disclosed
16.09.2022
Updated
11.10.2026 14:18

Sources and licenses

OSV / GitHub Advisory Database - PYSEC-2026-1019 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - PYSEC-2026-3215 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-mgmh-g2v6-mqw5 - CC BY 4.0

OSV / GitHub Advisory Database - PYSEC-2026-3351 - PyPA Advisory Database; CC BY 4.0

Vulnerability history: tensorflow-gpu

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (427) in the archive
Total entries
427
First → latest
04.2019 07.2024
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Critical 6
  • High 109
  • Medium 207
  • Low 105

Disclosures per year

  1. 2019: 7
  2. 2020: 35
  3. 2021: 200
  4. 2022: 166
  5. 2023: 18
  6. 2024: 1
  7. 2025: 0
  8. 2026: 0
Severity:
  1. High · 7.5 CVE-2023-33976 < 2.12.1 2.12.1
  2. High · 7.5 CVE-2023-25659 < 2.11.1 2.11.1
  3. High · 7.5 CVE-2023-25660 < 2.11.1 2.11.1
  4. High · 7.5 CVE-2023-25662 < 2.11.1 2.11.1
  5. High · 7.5 CVE-2023-25663 < 2.11.1 2.11.1
  6. High · 7.5 CVE-2023-25665 < 2.11.1 2.11.1
  7. High · 7.5 CVE-2023-25666 < 2.11.1 2.11.1
  8. High · 7.5 CVE-2023-25669 < 2.11.1 2.11.1
  9. High · 7.5 CVE-2023-25672 < 2.11.1 2.11.1
  10. High · 7.5 CVE-2023-25673 < 2.11.1 2.11.1
  11. High · 7.5 CVE-2023-25674 < 2.11.1 2.11.1
  12. High · 7.5 CVE-2023-25675 < 2.11.1 2.11.1
  13. High · 7.5 CVE-2023-25676 < 2.11.1 2.11.1
  14. High · 8.0 CVE-2023-25801 < 2.11.1 2.11.1
  15. High · 7.5 CVE-2023-27579 < 2.11.1 2.11.1
  16. High · 7.5 CVE-2023-25658 < 2.11.1 2.11.1
  17. High · 7.1 CVE-2022-41902 < 2.8.4, >= 2.9.0, < 2.9.3, >= 2.10.0, < 2.10.1 2.8.4, 2.9.3, 2.10.1
  18. High · 7.1 CVE-2022-41900 < 2.8.4, >= 2.9.0, < 2.9.3, >= 2.10.0, < 2.10.1 2.8.4, 2.9.3, 2.10.1
  19. TensorFlow vulnerable to `CHECK` failure in `AvgPoolOp` this entry
    Medium · 5.9 CVE-2022-35941 < 2.7.2, >= 2.8.0, < 2.8.1, >= 2.9.0, < 2.9.2 2.7.2, 2.8.1, 2.9.2
  20. High · 7.0 CVE-2022-35939 < 2.7.2, >= 2.8.0, < 2.8.1, >= 2.9.0, < 2.9.1 2.7.2, 2.8.1, 2.9.1
  21. High · 7.0 CVE-2022-35937 < 2.7.2, >= 2.8.0, < 2.8.1, >= 2.9.0, < 2.9.1 2.7.2, 2.8.1, 2.9.1
  22. High · 7.8 CVE-2022-29216 < 2.6.4, >= 2.7.0, < 2.7.2, >= 2.8.0, < 2.8.1 2.6.4, 2.7.2, 2.8.1
  23. High · 7.1 CVE-2022-29208 < 2.6.4, >= 2.7.0, < 2.7.2, >= 2.8.0, < 2.8.1 2.6.4, 2.7.2, 2.8.1
  24. Critical · 9.3 ghsa-h6gw-r52c-724r < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  25. High · 7.0 ghsa-43q8-3fv7-pr5x < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  26. High · 8.8 CVE-2022-23594 >= 2.7.0, < 2.7.1 2.7.1
  27. High · 8.8 CVE-2022-23560 < 2.5.3, >= 2.6.0, < 2.6.3 2.5.3, 2.6.3
  28. High · 7.1 CVE-2022-23563 < 2.5.3, >= 2.6.0, < 2.6.3 2.5.3, 2.6.3
  29. High · 8.1 CVE-2022-23592 >= 2.7.0, < 2.8.0 2.8.0
  30. High · 7.5 CVE-2022-23591 < 2.5.3, >= 2.6.0, < 2.6.3 2.5.3, 2.6.3
  31. High · 8.8 CVE-2022-23574 < 2.5.3, >= 2.6.0, < 2.6.3 2.5.3, 2.6.3
  32. High · 7.6 CVE-2022-23573 < 2.5.3, >= 2.6.0, < 2.6.3 2.5.3, 2.6.3
  33. High · 7.6 CVE-2022-23562 < 2.5.3, >= 2.6.0, < 2.6.3 2.5.3, 2.6.3
  34. High · 8.8 CVE-2022-23561 < 2.5.3, >= 2.6.0, < 2.6.3 2.5.3, 2.6.3
  35. High · 8.8 CVE-2022-23559 < 2.5.3, >= 2.6.0, < 2.6.3 2.5.3, 2.6.3
  36. High · 8.8 CVE-2022-23566 < 2.5.3, >= 2.6.0, < 2.6.3 2.5.3, 2.6.3
  37. High · 7.6 CVE-2022-23584 < 2.5.3, >= 2.6.0, < 2.6.3 2.5.3, 2.6.3
  38. High · 7.6 CVE-2022-23558 < 2.5.3, >= 2.6.0, < 2.6.3 2.5.3, 2.6.3
  39. High · 8.8 CVE-2022-23587 < 2.5.3, >= 2.6.0, < 2.6.3 2.5.3, 2.6.3
  40. High · 7.6 CVE-2022-21740 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  41. High · 6.5 CVE-2022-21741 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  42. High · 6.5 CVE-2022-21739 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  43. High · 6.5 CVE-2022-21737 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  44. High · 6.5 CVE-2022-21738 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  45. High · 6.5 CVE-2022-23569 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  46. High · 6.5 CVE-2022-21729 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  47. High · 6.5 CVE-2022-21734 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  48. High · 6.5 CVE-2022-21735 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  49. High · 7.6 CVE-2022-21736 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  50. High · 6.5 CVE-2022-21731 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  51. High · 6.5 CVE-2022-23567 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  52. High · 6.5 CVE-2022-23568 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  53. High · 8.1 CVE-2022-21726 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  54. High · 8.1 CVE-2022-21728 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  55. High · 7.6 CVE-2022-21727 < 2.5.3, >= 2.6.0, < 2.6.3 2.5.3, 2.6.3
  56. High · 8.1 CVE-2022-21730 < 2.5.3, >= 2.6.0, < 2.6.3, >= 2.7.0, < 2.7.1 2.5.3, 2.6.3, 2.7.1
  57. High · 7.8 CVE-2021-41221 >= 2.6.0, < 2.6.1, >= 2.5.0, < 2.5.2, < 2.4.4 2.6.1, 2.5.2, 2.4.4
  58. High · 7.8 CVE-2021-41220 >= 2.6.0, < 2.6.1 2.6.1
Show more (20) Showing 60 of 116

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.