Advisory record · GHSA-fq6p-6334-8gr4

Memory leak in decoding PNG images

CVSS 4.3 MediumEPSS 0.010 · 63rd percentile

Published by the GitHub Advisory Database at 9 Feb 2022, 23:26 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-fq6p-6334-8gr4 · BIT-tensorflow-2022-23585 · CVE-2022-23585 · PYSEC-2022-149 · PYSEC-2022-94 · PYSEC-2026-3174
Weakness (CWE)
CWE-401
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.

Memory leak in TensorFlow, tensorflow-cpu and tensorflow-gpu versions before 2.5.3, from 2.6.0 before 2.6.3, and from 2.7.0 before 2.7.1, when decoding invalid PNG images. An attacker who can supply a PNG image for decoding can cause memory to leak on each failed decode. Upgrade to 2.5.3, 2.6.3, or 2.7.1 according to your release line. The source gives no workaround.

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
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.010, the 63rd percentile, on 19 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.