<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 24 Oct 2026 01:40:25 +0000</lastBuildDate>
    <item>
      <title>BIT-tensorflow-2022-29197 — Missing validation causes denial of service in TensorFlow via `UnsortedSegmentJoin`</title>
      <link>https://cve.radiocsirt.org/vuln/bit-tensorflow-2022-29197</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: tensorflow&lt;/p&gt;
&lt;p&gt;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.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. The code assumes `num_segments` is a scalar but there is no validation for this before accessing its value. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: tensorflow&lt;/p&gt;
&lt;p&gt;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.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. The code assumes `num_segments` is a scalar but there is no validation for this before accessing its value. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-tensorflow-2022-29197</guid>
    </item>
    <item>
      <title>cnvd-2022-44175</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2022-44175</link>
      <description>cnvd-2022-44175</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2022-44175</guid>
    </item>
    <item>
      <title>EUVD-2026-232725</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-232725</link>
      <description>EUVD-2026-232725</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-232725</guid>
    </item>
    <item>
      <title>fkie_cve-2022-29197</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-29197</link>
      <description>&lt;p&gt;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.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. The code assumes `num_segments` is a scalar but there is no validation for this before accessing its value. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.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. The code assumes `num_segments` is a scalar but there is no validation for this before accessing its value. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-29197</guid>
    </item>
    <item>
      <title>GHSA-hrg5-737c-2p56 — Missing validation causes denial of service via `UnsortedSegmentJoin`</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hrg5-737c-2p56</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: tensorflow, PyPI: tensorflow-cpu, PyPI: tensorflow-gpu&lt;/p&gt;
&lt;p&gt;### Impact
The implementation of [`tf.raw_ops.UnsortedSegmentJoin`](https://github.com/tensorflow/tensorflow/blob/f3b9bf4c3c0597563b289c0512e98d4ce81f886e/tensorflow/core/kernels/unsorted_segment_join_op.cc#L92-L95) does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack:&lt;/p&gt;
&lt;p&gt;```python
import tensorflow as tf&lt;/p&gt;
&lt;p&gt;tf.raw_ops.UnsortedSegmentJoin(
  inputs=tf.constant(&amp;#34;this&amp;#34;, 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:&lt;/p&gt;
&lt;p&gt;```cc
const Tensor&amp;amp; num_segments_tensor = context-&amp;gt;input(2);
OP_REQUIRES(context, num_segments_tensor.NumElements() != 0,
            errors::InvalidArgument(&amp;#34;Number of segments cannot be empty.&amp;#34;));
auto num_segments = num_segments_tensor.scalar&amp;lt;NUM_SEGMENTS_TYPE&amp;gt;()();
```&lt;/p&gt;
&lt;p&gt;### Patches
We have patched the issue in GitHub commit [13d38a07ce9143e044aa737cfd7bb759d0e9b400](https://github.com/tensorflow/tensorflow/commit/13d38a07ce9143e044aa737cfd7bb759d0e9b400).&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECUR…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: tensorflow, PyPI: tensorflow-cpu, PyPI: tensorflow-gpu&lt;/p&gt;
&lt;p&gt;### Impact
The implementation of [`tf.raw_ops.UnsortedSegmentJoin`](https://github.com/tensorflow/tensorflow/blob/f3b9bf4c3c0597563b289c0512e98d4ce81f886e/tensorflow/core/kernels/unsorted_segment_join_op.cc#L92-L95) does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack:&lt;/p&gt;
&lt;p&gt;```python
import tensorflow as tf&lt;/p&gt;
&lt;p&gt;tf.raw_ops.UnsortedSegmentJoin(
  inputs=tf.constant(&amp;#34;this&amp;#34;, 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:&lt;/p&gt;
&lt;p&gt;```cc
const Tensor&amp;amp; num_segments_tensor = context-&amp;gt;input(2);
OP_REQUIRES(context, num_segments_tensor.NumElements() != 0,
            errors::InvalidArgument(&amp;#34;Number of segments cannot be empty.&amp;#34;));
auto num_segments = num_segments_tensor.scalar&amp;lt;NUM_SEGMENTS_TYPE&amp;gt;()();
```&lt;/p&gt;
&lt;p&gt;### Patches
We have patched the issue in GitHub commit [13d38a07ce9143e044aa737cfd7bb759d0e9b400](https://github.com/tensorflow/tensorflow/commit/13d38a07ce9143e044aa737cfd7bb759d0e9b400).&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECUR…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hrg5-737c-2p56</guid>
    </item>
    <item>
      <title>gsd-2022-29197</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-29197</link>
      <description>gsd-2022-29197</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-29197</guid>
    </item>
    <item>
      <title>PYSEC-2026-1009 — Missing validation causes denial of service via `UnsortedSegmentJoin`</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-1009</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: tensorflow-gpu&lt;/p&gt;
&lt;p&gt;### Impact
The implementation of [`tf.raw_ops.UnsortedSegmentJoin`](https://github.com/tensorflow/tensorflow/blob/f3b9bf4c3c0597563b289c0512e98d4ce81f886e/tensorflow/core/kernels/unsorted_segment_join_op.cc#L92-L95) does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack:&lt;/p&gt;
&lt;p&gt;```python
import tensorflow as tf&lt;/p&gt;
&lt;p&gt;tf.raw_ops.UnsortedSegmentJoin(
  inputs=tf.constant(&amp;#34;this&amp;#34;, 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:&lt;/p&gt;
&lt;p&gt;```cc
const Tensor&amp;amp; num_segments_tensor = context-&amp;gt;input(2);
OP_REQUIRES(context, num_segments_tensor.NumElements() != 0,
            errors::InvalidArgument(&amp;#34;Number of segments cannot be empty.&amp;#34;));
auto num_segments = num_segments_tensor.scalar&amp;lt;NUM_SEGMENTS_TYPE&amp;gt;()();
```&lt;/p&gt;
&lt;p&gt;### Patches
We have patched the issue in GitHub commit [13d38a07ce9143e044aa737cfd7bb759d0e9b400](https://github.com/tensorflow/tensorflow/commit/13d38a07ce9143e044aa737cfd7bb759d0e9b400).&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECUR…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: tensorflow-gpu&lt;/p&gt;
&lt;p&gt;### Impact
The implementation of [`tf.raw_ops.UnsortedSegmentJoin`](https://github.com/tensorflow/tensorflow/blob/f3b9bf4c3c0597563b289c0512e98d4ce81f886e/tensorflow/core/kernels/unsorted_segment_join_op.cc#L92-L95) does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack:&lt;/p&gt;
&lt;p&gt;```python
import tensorflow as tf&lt;/p&gt;
&lt;p&gt;tf.raw_ops.UnsortedSegmentJoin(
  inputs=tf.constant(&amp;#34;this&amp;#34;, 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:&lt;/p&gt;
&lt;p&gt;```cc
const Tensor&amp;amp; num_segments_tensor = context-&amp;gt;input(2);
OP_REQUIRES(context, num_segments_tensor.NumElements() != 0,
            errors::InvalidArgument(&amp;#34;Number of segments cannot be empty.&amp;#34;));
auto num_segments = num_segments_tensor.scalar&amp;lt;NUM_SEGMENTS_TYPE&amp;gt;()();
```&lt;/p&gt;
&lt;p&gt;### Patches
We have patched the issue in GitHub commit [13d38a07ce9143e044aa737cfd7bb759d0e9b400](https://github.com/tensorflow/tensorflow/commit/13d38a07ce9143e044aa737cfd7bb759d0e9b400).&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECUR…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-1009</guid>
    </item>
  </channel>
</rss>
