Advisory

PYSEC-2026-3241

Also known as: BIT-tensorflow-2022-23572, CVE-2022-23572, GHSA-rww7-2gpw-fv6j, PYSEC-2022-136, PYSEC-2022-81

Summary

Crash when type cannot be specialized in Tensorflow

Details

Impact
Under certain scenarios, TensorFlow can fail to specialize a type during shape inference:

void InferenceContext::PreInputInit(
    const OpDef& op_def, const std::vector<const Tensor*>& input_tensors,
    const std::vector<ShapeHandle>& input_tensors_as_shapes) {
  const auto ret = full_type::SpecializeType(attrs_, op_def);
  DCHECK(ret.status().ok()) << "while instantiating types: " << ret.status();
  ret_types_ = ret.ValueOrDie();
  // ... 
}

However, DCHECK is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the ValueOrDie line. This results in an assertion failure as ret contains an error Status, not a value. In the second case we also get a crash due to the assertion failure.
Patches
We have patched the issue in GitHub commit cb164786dc891ea11d3a900e90367c339305dc7b.

The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.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