Advisory record · GHSA-627q-g293-49q7

Abort caused by allocating a vector that is too large in Tensorflow

CVSS 6.5 MediumEPSS 0.0083 · 57th percentile

Published by the GitHub Advisory Database at 7 Feb 2022, 22:01 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-627q-g293-49q7 · BIT-tensorflow-2022-23580 · CVE-2022-23580 · PYSEC-2022-144 · PYSEC-2022-89 · PYSEC-2026-3113
Weakness (CWE)
CWE-400 · CWE-1284
Published
7 Feb 2022
Updated
13 Jul 2026

Machine-written summary

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

TensorFlow packages tensorflow, tensorflow-cpu and tensorflow-gpu are affected in versions before 2.5.3, from 2.6.0 before 2.6.3, and from 2.7.0 before 2.7.1. During shape inference, a large vector can be allocated based on a value in a user-controlled tensor, which can abort the process. The source gives few details about who can trigger this or how. Upgrade to 2.5.3, 2.6.3, 2.7.1 or later, where the issue is fixed.

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
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0083, the 57th percentile, on 9 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.