https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-06T11:08:45.811311+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bit-tensorflow-2020-26270 BIT-tensorflow-2020-26270 — CHECK-fail in LSTM with zero-length input in TensorFlow 2026-10-06T11:08:45.826630+00:00

Affected: Bitnami: tensorflow

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.

 https://cve.radiocsirt.org/vuln/cnvd-2021-00093 cnvd-2021-00093 2026-10-06T11:08:45.826688+00:00 cnvd-2021-00093 https://cve.radiocsirt.org/vuln/euvd-2026-46017 EUVD-2026-46017 2026-10-06T11:08:45.826705+00:00 EUVD-2026-46017 https://cve.radiocsirt.org/vuln/fkie_cve-2020-26270 fkie_cve-2020-26270 2026-10-06T11:08:45.826716+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-m648-33qf-v3gp GHSA-m648-33qf-v3gp — CHECK-fail in LSTM with zero-length input in TensorFlow 2026-10-06T11:08:45.826738+00:00

Affected: PyPI: tensorflow, PyPI: tensorflow-cpu, PyPI: tensorflow-gpu

### 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.

This can result in a query-of-death vulnerability, via denial of service, if users can control the input to the layer.

### 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.

Since this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive.

### 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.

 https://cve.radiocsirt.org/vuln/gsd-2020-26270 gsd-2020-26270 2026-10-06T11:08:45.826775+00:00 gsd-2020-26270 https://cve.radiocsirt.org/vuln/opensuse-su-2022:10014-1 openSUSE-SU-2022:10014-1 — Security update for tensorflow2 2026-10-06T11:08:45.826787+00:00

Security update for tensorflow2

 https://cve.radiocsirt.org/vuln/pysec-2020-256 PYSEC-2020-256 2026-10-06T11:08:45.826829+00:00

Affected: PyPI: tensorflow

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.