Advisory record · GHSA-wc4g-r73w-x8mm

Insecure temporary file in Tensorflow

CVSS 7.1 HighEPSS 0.0011 · 1st percentile

Published by the GitHub Advisory Database at 9 Feb 2022, 23:54 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-wc4g-r73w-x8mm · BIT-tensorflow-2022-23563 · CVE-2022-23563 · PYSEC-2022-127 · PYSEC-2022-72 · PYSEC-2026-3253
Weakness (CWE)
CWE-367 · CWE-668
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.

The tensorflow, tensorflow-cpu and tensorflow-gpu packages 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. The source describes a race condition in which TensorFlow uses the insecure tempfile.mktemp function, so another local process could create a file at the same path before TensorFlow does, and in some places a directory was meant to be created instead. The source does not describe the specific attack conditions or consequences in detail. Upgrade to tensorflow 2.5.3, 2.6.3, or 2.7.1, or the matching tensorflow-cpu or tensorflow-gpu version.

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.1 High 3.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0011, the 1st percentile, on 20 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.