Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2020-26270CHECK-fail in LSTM with zero-length input in TensorFlow

Description

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.

Timeline

  1. ID reserved

    By GitHub_M

  2. · 2 months later

    Published

  3. · 4 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2020-26270, by who scored it
Scored byCVSSScoreVector
GitHub_MCNA (assigner)3.1Medium4.4CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
NVDNVD · Modified3.1Low3.3CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (19 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.4.

Affected products

  • tensorflow · tensorflow

    • affected < 1.15.5
    • affected >= 2.0.0, < 2.0.4
    • affected >= 2.1.0, < 2.1.3
    • affected >= 2.2.0, < 2.2.2
    • affected >= 2.3.0, < 2.3.2

Affected packages

From reviewed advisories of the GitHub Advisory Database.

References

References2

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2020-26270 badge
[![CVE-2020-26270](https://cveledger.app/badge/CVE-2020-26270.svg)](https://cveledger.app/cve/CVE-2020-26270)

Record last updated .