Advisory record · GHSA-c582-c96p-r5cq

Memory exhaustion in Tensorflow

CVSS 4.3 MediumEPSS 0.0076 · 56th percentile

Published by the GitHub Advisory Database at 10 Feb 2022, 00:20 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-c582-c96p-r5cq · BIT-tensorflow-2022-21732 · CVE-2022-21732 · PYSEC-2022-111 · PYSEC-2022-56 · PYSEC-2026-3158
Weakness (CWE)
CWE-400 · CWE-770
Published
10 Feb 2022
Updated
10 Sept 2026

Machine-written summary

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

The tensorflow, tensorflow-cpu and tensorflow-gpu packages are affected before 2.5.3, from 2.6.0 before 2.6.3, and from 2.7.0 before 2.7.1. The num_threads argument of ThreadPoolHandle has no upper bound, so an attacker can cause a denial of service by exhausting memory. Upgrade to 2.5.3, 2.6.3, or 2.7.1.

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

Timeline

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