Advisory record · GHSA-247x-2f9f-5wp7

Stack overflow in TensorFlow

CVSS 7.5 HighEPSS 0.0080 · 57th percentile

Published by the GitHub Advisory Database at 9 Feb 2022, 23:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
tensorflowPyPI<2.5.3 || >=2.6.0, <2.6.3 || >=2.7.0, <2.7.12.5.3, 2.6.3, 2.7.1
tensorflow-cpuPyPI<2.5.3 || >=2.6.0, <2.6.3 || >=2.7.0, <2.7.12.5.3, 2.6.3, 2.7.1
tensorflow-gpuPyPI<2.5.3 || >=2.6.0, <2.6.3 || >=2.7.0, <2.7.12.5.3, 2.6.3, 2.7.1
Identifiers
GHSA-247x-2f9f-5wp7 · BIT-tensorflow-2022-23591 · CVE-2022-23591 · PYSEC-2022-100 · PYSEC-2022-155 · PYSEC-2026-3084
Weakness (CWE)
CWE-400 · CWE-674
Published
9 Feb 2022
Updated
13 Jul 2026

Machine-written summary

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

Stack overflow in the tensorflow, tensorflow-cpu and tensorflow-gpu packages affects versions before 2.5.3, from 2.6.0 before 2.6.3, and from 2.7.0 before 2.7.1. A crafted GraphDef containing a self-recursive function, such as one loaded from a SavedModel, can trigger unbounded recursion during execution, causing a stack overflow. The source gives few details on the exact attacker access required. Upgrade to 2.5.3, 2.6.3, or 2.7.1 depending on your release line.

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
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0080, the 57th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:59 UTC First seen by agentprime
  2. 31 Oct 2026, 14:59 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.