<?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>Wed, 07 Oct 2026 15:33:09 +0000</lastBuildDate>
    <item>
      <title>BIT-tensorflow-2022-29204 — Missing validation causes denial of service in TensorFlow via `Conv3DBackpropFilterV2`</title>
      <link>https://cve.radiocsirt.org/vuln/bit-tensorflow-2022-29204</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 positive scalar but there is no validation. Since this value is used to allocate the output tensor, a negative value would result in a `CHECK`-failure (assertion failure), as per TFSA-2021-198. 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 positive scalar but there is no validation. Since this value is used to allocate the output tensor, a negative value would result in a `CHECK`-failure (assertion failure), as per TFSA-2021-198. 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-29204</guid>
    </item>
    <item>
      <title>cnvd-2022-44170</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2022-44170</link>
      <description>cnvd-2022-44170</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2022-44170</guid>
    </item>
    <item>
      <title>EUVD-2026-232719</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-232719</link>
      <description>EUVD-2026-232719</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-232719</guid>
    </item>
    <item>
      <title>fkie_cve-2022-29204</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-29204</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 positive scalar but there is no validation. Since this value is used to allocate the output tensor, a negative value would result in a `CHECK`-failure (assertion failure), as per TFSA-2021-198. 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 positive scalar but there is no validation. Since this value is used to allocate the output tensor, a negative value would result in a `CHECK`-failure (assertion failure), as per TFSA-2021-198. 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-29204</guid>
    </item>
    <item>
      <title>GHSA-hx9q-2mx4-m4pg — Missing validation causes denial of service via `Conv3DBackpropFilterV2`</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hx9q-2mx4-m4pg</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#L83-L148) 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.strings.unsorted_segment_join(
  inputs=[&amp;#39;123&amp;#39;],
  segment_ids=[0],
  num_segments=-1)
```&lt;/p&gt;
&lt;p&gt;The code assumes `num_segments` is a positive scalar but there is no validation:&lt;/p&gt;
&lt;p&gt;```cc
const Tensor&amp;amp; num_segments_tensor = context-&amp;gt;input(2);
auto num_segments = num_segments_tensor.scalar&amp;lt;NUM_SEGMENTS_TYPE&amp;gt;()();
// ...
Tensor* output_tensor = nullptr;
TensorShape output_shape =
    GetOutputShape(input_shape, segment_id_shape, num_segments);
```&lt;/p&gt;
&lt;p&gt;Since this value is used to allocate the output tensor, a negative value would result in a `CHECK`-failure (assertion failure), as per [TFSA-2021-198](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-198.md).&lt;/p&gt;
&lt;p&gt;### Patches 
We have patched the issue in GitHub commit [84563f265f28b3c36a15335c8b005d405260e943](https://github.com/tensorflow/tensorflow/commit/84563f265f28b3c36a15335c8b005d405260e943) and GitHub commit [20cb18724b0bf6c09071a3f53434c4eec53cc147](https://github.com/tensorflow/tensorflow/commit/20cb18724b0bf6c09071a3f53434c4eec53cc147).
  
The fix will be included in TensorFlow 2.9.0. We will also cherrypi…&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#L83-L148) 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.strings.unsorted_segment_join(
  inputs=[&amp;#39;123&amp;#39;],
  segment_ids=[0],
  num_segments=-1)
```&lt;/p&gt;
&lt;p&gt;The code assumes `num_segments` is a positive scalar but there is no validation:&lt;/p&gt;
&lt;p&gt;```cc
const Tensor&amp;amp; num_segments_tensor = context-&amp;gt;input(2);
auto num_segments = num_segments_tensor.scalar&amp;lt;NUM_SEGMENTS_TYPE&amp;gt;()();
// ...
Tensor* output_tensor = nullptr;
TensorShape output_shape =
    GetOutputShape(input_shape, segment_id_shape, num_segments);
```&lt;/p&gt;
&lt;p&gt;Since this value is used to allocate the output tensor, a negative value would result in a `CHECK`-failure (assertion failure), as per [TFSA-2021-198](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-198.md).&lt;/p&gt;
&lt;p&gt;### Patches 
We have patched the issue in GitHub commit [84563f265f28b3c36a15335c8b005d405260e943](https://github.com/tensorflow/tensorflow/commit/84563f265f28b3c36a15335c8b005d405260e943) and GitHub commit [20cb18724b0bf6c09071a3f53434c4eec53cc147](https://github.com/tensorflow/tensorflow/commit/20cb18724b0bf6c09071a3f53434c4eec53cc147).
  
The fix will be included in TensorFlow 2.9.0. We will also cherrypi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hx9q-2mx4-m4pg</guid>
    </item>
    <item>
      <title>gsd-2022-29204</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-29204</link>
      <description>gsd-2022-29204</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-29204</guid>
    </item>
    <item>
      <title>PYSEC-2026-1010 — Missing validation causes denial of service via `Conv3DBackpropFilterV2`</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-1010</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#L83-L148) 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.strings.unsorted_segment_join(
  inputs=[&amp;#39;123&amp;#39;],
  segment_ids=[0],
  num_segments=-1)
```&lt;/p&gt;
&lt;p&gt;The code assumes `num_segments` is a positive scalar but there is no validation:&lt;/p&gt;
&lt;p&gt;```cc
const Tensor&amp;amp; num_segments_tensor = context-&amp;gt;input(2);
auto num_segments = num_segments_tensor.scalar&amp;lt;NUM_SEGMENTS_TYPE&amp;gt;()();
// ...
Tensor* output_tensor = nullptr;
TensorShape output_shape =
    GetOutputShape(input_shape, segment_id_shape, num_segments);
```&lt;/p&gt;
&lt;p&gt;Since this value is used to allocate the output tensor, a negative value would result in a `CHECK`-failure (assertion failure), as per [TFSA-2021-198](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-198.md).&lt;/p&gt;
&lt;p&gt;### Patches 
We have patched the issue in GitHub commit [84563f265f28b3c36a15335c8b005d405260e943](https://github.com/tensorflow/tensorflow/commit/84563f265f28b3c36a15335c8b005d405260e943) and GitHub commit [20cb18724b0bf6c09071a3f53434c4eec53cc147](https://github.com/tensorflow/tensorflow/commit/20cb18724b0bf6c09071a3f53434c4eec53cc147).
  
The fix will be included in TensorFlow 2.9.0. We will also cherrypi…&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#L83-L148) 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.strings.unsorted_segment_join(
  inputs=[&amp;#39;123&amp;#39;],
  segment_ids=[0],
  num_segments=-1)
```&lt;/p&gt;
&lt;p&gt;The code assumes `num_segments` is a positive scalar but there is no validation:&lt;/p&gt;
&lt;p&gt;```cc
const Tensor&amp;amp; num_segments_tensor = context-&amp;gt;input(2);
auto num_segments = num_segments_tensor.scalar&amp;lt;NUM_SEGMENTS_TYPE&amp;gt;()();
// ...
Tensor* output_tensor = nullptr;
TensorShape output_shape =
    GetOutputShape(input_shape, segment_id_shape, num_segments);
```&lt;/p&gt;
&lt;p&gt;Since this value is used to allocate the output tensor, a negative value would result in a `CHECK`-failure (assertion failure), as per [TFSA-2021-198](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-198.md).&lt;/p&gt;
&lt;p&gt;### Patches 
We have patched the issue in GitHub commit [84563f265f28b3c36a15335c8b005d405260e943](https://github.com/tensorflow/tensorflow/commit/84563f265f28b3c36a15335c8b005d405260e943) and GitHub commit [20cb18724b0bf6c09071a3f53434c4eec53cc147](https://github.com/tensorflow/tensorflow/commit/20cb18724b0bf6c09071a3f53434c4eec53cc147).
  
The fix will be included in TensorFlow 2.9.0. We will also cherrypi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-1010</guid>
    </item>
  </channel>
</rss>
