<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T06:54:53.588130+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2020-26270</id>
    <title>CVE-2020-26270 — CHECK-fail in LSTM with zero-length input in TensorFlow</title>
    <updated>2026-10-06T06:54:53.619468+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> tensorflow</p>
<p>In affected versions of TensorFlow running an LSTM/GRU model where the LSTM/GRU layer receives an input with zero-length results in a CHECK failure when using the CUDA backend. This can result in a query-of-death vulnerability, via denial of service, if users can control the input to the layer. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2020-26270"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-m648-33qf-v3gp</id>
    <title>GHSA-m648-33qf-v3gp — CHECK-fail in LSTM with zero-length input in TensorFlow</title>
    <updated>2026-10-06T06:54:53.619527+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: tensorflow, PyPI: tensorflow-cpu, PyPI: tensorflow-gpu</p>
<p>### Impact
Running an LSTM/GRU model where the LSTM/GRU layer receives an input with zero-length results in a `CHECK` failure when using the CUDA backend.</p>
<p>This can result in a query-of-death vulnerability, via denial of service, if users can control the input to the layer.</p>
<p>### Patches
We have patched the issue in GitHub commit [14755416e364f17fb1870882fa778c7fec7f16e3](https://github.com/tensorflow/tensorflow/commit/14755416e364f17fb1870882fa778c7fec7f16e3) and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.</p>
<p>Since this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive.</p>
<p>### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-m648-33qf-v3gp"/>
  </entry>
</feed>
