<?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>Tue, 06 Oct 2026 16:44:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-41201 — Unitialized access in `EinsumHelper::ParseEquation`</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-41201</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; tensorflow&lt;/p&gt;
&lt;p&gt;TensorFlow is an open source platform for machine learning. In affeced versions during execution, `EinsumHelper::ParseEquation()` is supposed to set the flags in `input_has_ellipsis` vector and `*output_has_ellipsis` boolean to indicate whether there is ellipsis in the corresponding inputs and output. However, the code only changes these flags to `true` and never assigns `false`. This results in unitialized variable access if callers assume that `EinsumHelper::ParseEquation()` always sets these flags. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; tensorflow&lt;/p&gt;
&lt;p&gt;TensorFlow is an open source platform for machine learning. In affeced versions during execution, `EinsumHelper::ParseEquation()` is supposed to set the flags in `input_has_ellipsis` vector and `*output_has_ellipsis` boolean to indicate whether there is ellipsis in the corresponding inputs and output. However, the code only changes these flags to `true` and never assigns `false`. This results in unitialized variable access if callers assume that `EinsumHelper::ParseEquation()` always sets these flags. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-41201</guid>
    </item>
    <item>
      <title>GHSA-j86v-p27c-73fm — Unitialized access in `EinsumHelper::ParseEquation`</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-j86v-p27c-73fm</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
During execution, [`EinsumHelper::ParseEquation()`](https://github.com/tensorflow/tensorflow/blob/e0b6e58c328059829c3eb968136f17aa72b6c876/tensorflow/core/kernels/linalg/einsum_op_impl.h#L126-L181) is supposed to set the flags in `input_has_ellipsis` vector and `*output_has_ellipsis` boolean to indicate whether there is ellipsis in the corresponding inputs and output.&lt;/p&gt;
&lt;p&gt;However, the code only changes these flags to `true` and never assigns `false`.&lt;/p&gt;
&lt;p&gt;```cc
for (int i = 0; i &amp;lt; num_inputs; ++i) {
  input_label_counts-&amp;gt;at(i).resize(num_labels);
  for (const int label : input_labels-&amp;gt;at(i)) {
    if (label != kEllipsisLabel)
      input_label_counts-&amp;gt;at(i)[label] += 1;
    else
      input_has_ellipsis-&amp;gt;at(i) = true;
  }
}
output_label_counts-&amp;gt;resize(num_labels);
for (const int label : *output_labels) {
  if (label != kEllipsisLabel)
    output_label_counts-&amp;gt;at(label) += 1;
  else
    *output_has_ellipsis = true;
}
```&lt;/p&gt;
&lt;p&gt;This results in unitialized variable access if callers assume that `EinsumHelper::ParseEquation()` always sets these flags.&lt;/p&gt;
&lt;p&gt;### Patches
We have patched the issue in GitHub commit [f09caa532b6e1ac8d2aa61b7832c78c5b79300c6](https://github.com/tensorflow/tensorflow/commit/f09caa532b6e1ac8d2aa61b7832c78c5b79300c6).&lt;/p&gt;
&lt;p&gt;The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.&lt;/p&gt;
&lt;p&gt;### For more information
Please consult [ou…&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
During execution, [`EinsumHelper::ParseEquation()`](https://github.com/tensorflow/tensorflow/blob/e0b6e58c328059829c3eb968136f17aa72b6c876/tensorflow/core/kernels/linalg/einsum_op_impl.h#L126-L181) is supposed to set the flags in `input_has_ellipsis` vector and `*output_has_ellipsis` boolean to indicate whether there is ellipsis in the corresponding inputs and output.&lt;/p&gt;
&lt;p&gt;However, the code only changes these flags to `true` and never assigns `false`.&lt;/p&gt;
&lt;p&gt;```cc
for (int i = 0; i &amp;lt; num_inputs; ++i) {
  input_label_counts-&amp;gt;at(i).resize(num_labels);
  for (const int label : input_labels-&amp;gt;at(i)) {
    if (label != kEllipsisLabel)
      input_label_counts-&amp;gt;at(i)[label] += 1;
    else
      input_has_ellipsis-&amp;gt;at(i) = true;
  }
}
output_label_counts-&amp;gt;resize(num_labels);
for (const int label : *output_labels) {
  if (label != kEllipsisLabel)
    output_label_counts-&amp;gt;at(label) += 1;
  else
    *output_has_ellipsis = true;
}
```&lt;/p&gt;
&lt;p&gt;This results in unitialized variable access if callers assume that `EinsumHelper::ParseEquation()` always sets these flags.&lt;/p&gt;
&lt;p&gt;### Patches
We have patched the issue in GitHub commit [f09caa532b6e1ac8d2aa61b7832c78c5b79300c6](https://github.com/tensorflow/tensorflow/commit/f09caa532b6e1ac8d2aa61b7832c78c5b79300c6).&lt;/p&gt;
&lt;p&gt;The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.&lt;/p&gt;
&lt;p&gt;### For more information
Please consult [ou…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-j86v-p27c-73fm</guid>
    </item>
  </channel>
</rss>
