Advisory

PYSEC-2026-3266

Also known as: BIT-tensorflow-2022-29208, CVE-2022-29208, GHSA-2r2f-g8mw-9gvr, PYSEC-2026-3088, PYSEC-2026-943

Summary

Segfault and OOB write due to incomplete validation in EditDistance in TensorFlow

Details

Impact
The implementation of [tf.raw_ops.EditDistance]() has incomplete validation. Users can pass negative values to cause a segmentation fault based denial of service:

import tensorflow as tf

hypothesis_indices = tf.constant(-1250999896764, shape=[3, 3], dtype=tf.int64) 
hypothesis_values = tf.constant(0, shape=[3], dtype=tf.int64)
hypothesis_shape = tf.constant(0, shape=[3], dtype=tf.int64)

truth_indices = tf.constant(-1250999896764, shape=[3, 3], dtype=tf.int64)
truth_values = tf.constant(2, shape=[3], dtype=tf.int64)
truth_shape = tf.constant(2, shape=[3], dtype=tf.int64) 

tf.raw_ops.EditDistance(
  hypothesis_indices=hypothesis_indices,
  hypothesis_values=hypothesis_values,
  hypothesis_shape=hypothesis_shape,
  truth_indices=truth_indices,
  truth_values=truth_values,
  truth_shape=truth_shape)

In multiple places throughout the code, we are computing an index for a write operation:

if (g_truth == g_hypothesis) {
  auto loc = std::inner_product(g_truth.begin(), g_truth.end(),
                                output_strides.begin(), int64_t{0});
  OP_REQUIRES(
      ctx, loc < output_elements,
      errors::Internal("Got an inner product ", loc,
                       " which would require in writing to outside of "
                       "the buffer for the output tensor (max elements ",
                       output_elements, ")"));
  output_t(loc) =
      gtl::LevenshteinDistance<T>(truth_seq, hypothesis_seq, cmp);
  // ...
}

However, the existing validation only checks against the upper bound of the array. Hence, it is possible to write before the array by massaging the input to generate negative values for loc.

Patches
We have patched the issue in GitHub commit 30721cf564cb029d34535446d6a5a6357bebc8e7.

The fix will be included in TensorFlow 2.9.0. We will also cherrypick this commit on TensorFlow 2.8.1, TensorFlow 2.7.2, and TensorFlow 2.6.4, 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.

Attribution
This vulnerability has been reported by Neophytos Christou from Secure Systems Lab at Brown University.

Severity

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

Dates

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

Affected packages and fixes

tensorflow-cpu

PyPI · All systems

Affected

  • introduced 0, fixed 2.6.4, introduced 2.7.0, fixed 2.7.2, introduced 2.8.0, fixed 2.8.1 (ecosystem)

Fixed versions

2.6.4, 2.7.2, 2.8.1

Fix

  • Fixed version 2.6.4
    pip install --upgrade tensorflow-cpu==2.6.4
  • Fixed version 2.7.2
    pip install --upgrade tensorflow-cpu==2.7.2
  • Fixed version 2.8.1
    pip install --upgrade tensorflow-cpu==2.8.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