Advisory

PYSEC-2026-3138

Also known as: BIT-tensorflow-2022-23578, CVE-2022-23578, GHSA-8r7c-3cm2-3h8f, PYSEC-2022-142, PYSEC-2022-87

Summary

Memory leak in Tensorflow

Details

Impact
If a graph node is invalid, TensorFlow can leak memory in the implementation of `ImmutableExecutorState::Initialize`:

Status s = params_.create_kernel(n->properties(), &item->kernel);
if (!s.ok()) {
  item->kernel = nullptr;
  s = AttachDef(s, *n);
  return s;           
}                     

Here, we set item->kernel to nullptr but it is a simple OpKernel* pointer so the memory that was previously allocated to it would leak.

Patches
We have patched the issue in GitHub commit c79ccba517dbb1a0ccb9b01ee3bd2a63748b60dd.
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.

For more information
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Severity

Medium Basis: CVSS v3 score 4.3, vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Dates

Published
2026-07-09 16:49 UTC
Modified
2026-07-13 16:42 UTC

Affected packages and fixes

tensorflow

PyPI · All systems

Affected

  • introduced 0, fixed 2.5.3, introduced 2.6.0, fixed 2.6.3, introduced 2.7.0, fixed 2.7.1 (ecosystem)

Fixed versions

2.5.3, 2.6.3, 2.7.1

Fix

  • Fixed version 2.5.3
    pip install --upgrade tensorflow==2.5.3
  • Fixed version 2.6.3
    pip install --upgrade tensorflow==2.6.3
  • Fixed version 2.7.1
    pip install --upgrade tensorflow==2.7.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: PyPA Advisory Database · CC BY 4.0

Sources & licences