<?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>Sun, 25 Oct 2026 22:54:11 +0000</lastBuildDate>
    <item>
      <title>cnvd-2021-00089</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2021-00089</link>
      <description>cnvd-2021-00089</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2021-00089</guid>
    </item>
    <item>
      <title>EUVD-2026-46033</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-46033</link>
      <description>EUVD-2026-46033</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-46033</guid>
    </item>
    <item>
      <title>fkie_cve-2020-26269</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-26269</link>
      <description>&lt;p&gt;In TensorFlow release candidate versions 2.4.0rc*, the general implementation for matching filesystem paths to globbing pattern is vulnerable to an access out of bounds of the array holding the directories. There are multiple invariants and preconditions that are assumed by the parallel implementation of GetMatchingPaths but are not verified by the PRs introducing it (#40861 and #44310). Thus, we are completely rewriting the implementation to fully specify and validate these. This is patched in version 2.4.0. This issue only impacts master branch and the release candidates for TF version 2.4. The final release of the 2.4 release will be patched.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In TensorFlow release candidate versions 2.4.0rc*, the general implementation for matching filesystem paths to globbing pattern is vulnerable to an access out of bounds of the array holding the directories. There are multiple invariants and preconditions that are assumed by the parallel implementation of GetMatchingPaths but are not verified by the PRs introducing it (#40861 and #44310). Thus, we are completely rewriting the implementation to fully specify and validate these. This is patched in version 2.4.0. This issue only impacts master branch and the release candidates for TF version 2.4. The final release of the 2.4 release will be patched.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-26269</guid>
    </item>
    <item>
      <title>GHSA-9jjw-hf72-3mxw — TensorFlow vulnerable to heap out of bounds read in filesystem glob matching</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9jjw-hf72-3mxw</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 general implementation for matching filesystem paths to globbing pattern is vulnerable to an access out of bounds of [the array holding the directories](https://github.com/tensorflow/tensorflow/blob/458c6260265c46ebaf18052d6c61aea4b6b40926/tensorflow/core/platform/file_system_helper.cc#L127):&lt;/p&gt;
&lt;p&gt;```cc
if (!fs-&amp;gt;Match(child_path, dirs[dir_index])) { ... }
```&lt;/p&gt;
&lt;p&gt;Since `dir_index` is [unconditionaly incremented](https://github.com/tensorflow/tensorflow/blob/458c6260265c46ebaf18052d6c61aea4b6b40926/tensorflow/core/platform/file_system_helper.cc#L106) outside of the lambda function where the vulnerable pattern occurs, this results in an access out of bounds issue under certain scenarios. For example, if `/tmp/x` is a directory that only contains a single file `y`, then the following scenario will cause a crash due to the out of bounds read:&lt;/p&gt;
&lt;p&gt;```python
&amp;gt;&amp;gt;&amp;gt; tf.io.gfile.glob(&amp;#39;/tmp/x/&amp;#39;)
Segmentation fault
```&lt;/p&gt;
&lt;p&gt;There are multiple invariants and preconditions that are assumed by the parallel implementation of `GetMatchingPaths` but are not verified by the PRs introducing it ([#40861](https://github.com/tensorflow/tensorflow/pull/40861) and [#44310](https://github.com/tensorflow/tensorflow/pull/44310)). Thus, we are completely rewriting the implementation to fully specify and validate these.&lt;/p&gt;
&lt;p&gt;### Patches
We have patched the issue in GitHub commit [8b5b9dc96666a3a5d27fad7179ff215e3b74b67c](https://github.com/tensorflow/tensorflow/commit/8b5b9dc96666a3a5d27fad7179ff215e3b74b67c…&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 general implementation for matching filesystem paths to globbing pattern is vulnerable to an access out of bounds of [the array holding the directories](https://github.com/tensorflow/tensorflow/blob/458c6260265c46ebaf18052d6c61aea4b6b40926/tensorflow/core/platform/file_system_helper.cc#L127):&lt;/p&gt;
&lt;p&gt;```cc
if (!fs-&amp;gt;Match(child_path, dirs[dir_index])) { ... }
```&lt;/p&gt;
&lt;p&gt;Since `dir_index` is [unconditionaly incremented](https://github.com/tensorflow/tensorflow/blob/458c6260265c46ebaf18052d6c61aea4b6b40926/tensorflow/core/platform/file_system_helper.cc#L106) outside of the lambda function where the vulnerable pattern occurs, this results in an access out of bounds issue under certain scenarios. For example, if `/tmp/x` is a directory that only contains a single file `y`, then the following scenario will cause a crash due to the out of bounds read:&lt;/p&gt;
&lt;p&gt;```python
&amp;gt;&amp;gt;&amp;gt; tf.io.gfile.glob(&amp;#39;/tmp/x/&amp;#39;)
Segmentation fault
```&lt;/p&gt;
&lt;p&gt;There are multiple invariants and preconditions that are assumed by the parallel implementation of `GetMatchingPaths` but are not verified by the PRs introducing it ([#40861](https://github.com/tensorflow/tensorflow/pull/40861) and [#44310](https://github.com/tensorflow/tensorflow/pull/44310)). Thus, we are completely rewriting the implementation to fully specify and validate these.&lt;/p&gt;
&lt;p&gt;### Patches
We have patched the issue in GitHub commit [8b5b9dc96666a3a5d27fad7179ff215e3b74b67c](https://github.com/tensorflow/tensorflow/commit/8b5b9dc96666a3a5d27fad7179ff215e3b74b67c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9jjw-hf72-3mxw</guid>
    </item>
    <item>
      <title>gsd-2020-26269</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-26269</link>
      <description>gsd-2020-26269</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-26269</guid>
    </item>
    <item>
      <title>PYSEC-2020-141</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2020-141</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: tensorflow&lt;/p&gt;
&lt;p&gt;In TensorFlow release candidate versions 2.4.0rc*, the general implementation for matching filesystem paths to globbing pattern is vulnerable to an access out of bounds of the array holding the directories. There are multiple invariants and preconditions that are assumed by the parallel implementation of GetMatchingPaths but are not verified by the PRs introducing it (#40861 and #44310). Thus, we are completely rewriting the implementation to fully specify and validate these. This is patched in version 2.4.0. This issue only impacts master branch and the release candidates for TF version 2.4. The final release of the 2.4 release will be patched.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: tensorflow&lt;/p&gt;
&lt;p&gt;In TensorFlow release candidate versions 2.4.0rc*, the general implementation for matching filesystem paths to globbing pattern is vulnerable to an access out of bounds of the array holding the directories. There are multiple invariants and preconditions that are assumed by the parallel implementation of GetMatchingPaths but are not verified by the PRs introducing it (#40861 and #44310). Thus, we are completely rewriting the implementation to fully specify and validate these. This is patched in version 2.4.0. This issue only impacts master branch and the release candidates for TF version 2.4. The final release of the 2.4 release will be patched.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2020-141</guid>
    </item>
  </channel>
</rss>
