Advisory

PYSEC-2026-3204

Also known as: BIT-tensorflow-2022-23571, CVE-2022-23571, GHSA-j3mj-fhpq-qqjj, PYSEC-2022-135, PYSEC-2022-80

Summary

Reachable Assertion in Tensorflow

Details

Impact
When decoding a tensor from protobuf, a TensorFlow process can encounter cases where a CHECK assertion is invalidated based on user controlled arguments, if the tensors have an invalid dtype and 0 elements or an invalid shape. This allows attackers to cause denial of services in TensorFlow processes.

Patches
We have patched the issue in GitHub commit 5b491cd5e41ad63735161cec9c2a568172c8b6a3.

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 6.5, vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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