Missing validation causes denial of service via `UnsortedSegmentJoin`
Impact
The implementation of tf.raw_ops.UnsortedSegmentJoin does not fully validate the input arguments. This results in a CHECK-failure which can be used to trigger a denial of service attack:
import tensorflow as tf
tf.raw_ops.UnsortedSegmentJoin(
inputs=tf.constant("this", shape=[12], dtype=tf.string),
segment_ids=tf.constant(0, shape=[12], dtype=tf.int64),
num_segments=tf.constant(0, shape=[12], dtype=tf.int64))The code assumes num_segments is a scalar but there is no validation for this before accessing its value:
const Tensor& num_segments_tensor = context->input(2);
OP_REQUIRES(context, num_segments_tensor.NumElements() != 0,
errors::InvalidArgument("Number of segments cannot be empty."));
auto num_segments = num_segments_tensor.scalar<NUM_SEGMENTS_TYPE>()();Patches
We have patched the issue in GitHub commit 13d38a07ce9143e044aa737cfd7bb759d0e9b400.
The fix will be included in TensorFlow 2.9.0. We will also cherrypick this commit on TensorFlow 2.8.1, TensorFlow 2.7.2, and TensorFlow 2.6.4, 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 Neophytos Christou from Secure Systems Lab at Brown University.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Python (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 |
| Python (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 |
| Python (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 |
References
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hrg5-737c-2p56
- https://nvd.nist.gov/vuln/detail/CVE-2022-29197
- https://github.com/tensorflow/tensorflow/commit/13d38a07ce9143e044aa737cfd7bb759d0e9b400
- https://github.com/tensorflow/tensorflow
- https://github.com/tensorflow/tensorflow/blob/f3b9bf4c3c0597563b289c0512e98d4ce81f886e/tensorflow/core/kernels/unsorted_segment_join_op.cc#L92-L95
- https://github.com/tensorflow/tensorflow/releases/tag/v2.6.4
- https://github.com/tensorflow/tensorflow/releases/tag/v2.7.2
- https://github.com/tensorflow/tensorflow/releases/tag/v2.8.1
- https://github.com/tensorflow/tensorflow/releases/tag/v2.9.0
- https://pypi.org/project/tensorflow-gpu
- https://github.com/advisories/GHSA-hrg5-737c-2p56
- https://pypi.org/project/tensorflow
- https://pypi.org/project/tensorflow-cpu
- CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H- Weakness (CWE)
CWE-20- Platform
- Python (PyPI)
- Package
tensorflow, tensorflow-cpu, tensorflow-gpu- Disclosed
- 24.05.2022
- Updated
- 11.10.2026 14:17
Sources and licenses
OSV / GitHub Advisory Database - PYSEC-2026-1009 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2026-3202 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-hrg5-737c-2p56 - CC BY 4.0
OSV / GitHub Advisory Database - PYSEC-2026-3341 - PyPA Advisory Database; CC BY 4.0
Vulnerability history: tensorflow-cpu
All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 430
- First → latest
- 04.2019 07.2024
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 6
- High 111
- Medium 208
- Low 105
Disclosures per year
- 2019: 7
- 2020: 35
- 2021: 200
- 2022: 166
- 2023: 21
- 2024: 1
- 2025: 0
- 2026: 0
-
Missing validation causes denial of service via `UnsortedSegmentJoin` this entry
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.