Advisory record · GHSA-2vv3-56qg-g2cf

Missing validation causes denial of service via `LSTMBlockCell`

CVSS 5.5 MediumEPSS 0.0032 · 25th percentile

Published by the GitHub Advisory Database at 24 May 2022, 22:10 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
tensorflowPyPI<2.6.4 || >=2.7.0, <2.7.2 || >=2.8.0, <2.8.12.6.4, 2.7.2, 2.8.1
tensorflow-cpuPyPI<2.6.4 || >=2.7.0, <2.7.2 || >=2.8.0, <2.8.12.6.4, 2.7.2, 2.8.1
tensorflow-gpuPyPI<2.6.4 || >=2.7.0, <2.7.2 || >=2.8.0, <2.8.12.6.4, 2.7.2, 2.8.1
Identifiers
GHSA-2vv3-56qg-g2cf · BIT-tensorflow-2022-29200 · CVE-2022-29200 · PYSEC-2026-3089 · PYSEC-2026-3267 · PYSEC-2026-944
Weakness (CWE)
CWE-20 · CWE-1284
Published
24 May 2022
Updated
13 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Missing input validation in the TensorFlow `tf.raw_ops.LSTMBlockCell` operation affects the tensorflow, tensorflow-cpu and tensorflow-gpu packages in versions before 2.6.4, from 2.7.0 before 2.7.2, and from 2.8.0 before 2.8.1. The operation does not check the ranks of its arguments, so a crafted call can trigger a CHECK failure and crash the process, causing denial of service. Upgrade to 2.6.4, 2.7.2, 2.8.1 or later.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.5 Medium 3.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0032, the 25th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:02 UTC First seen by agentprime
  2. 31 Oct 2026, 15:02 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.