Advisory

PYSEC-2026-3229

Also known as: BIT-tensorflow-2022-23573, CVE-2022-23573, GHSA-q85f-69q7-55h2, PYSEC-2022-137, PYSEC-2022-82

Summary

Uninitialized variable access in Tensorflow

Details

Impact
The implementation of `AssignOp` can result in copying unitialized data to a new tensor. This later results in undefined behavior.

The implementation has a check that the left hand side of the assignment is initialized (to minimize number of allocations), but does not check that the right hand side is also initialized.

Patches
We have patched the issue in GitHub commit ef1d027be116f25e25bb94a60da491c2cf55bd0b.

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

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

Dates

Published
2026-07-09 16:49 UTC
Modified
2026-07-13 16:43 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