PT-2026-59889 · Pypi · Tensorflow-Cpu
Published
2026-07-09
·
Updated
2026-07-09
CVSS v3.1
5.5
Medium
| Vector | AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Impact
There is a potential for segfault / denial of service in TensorFlow by calling
tf.compat.v1.* ops which don't yet have support for quantized types (added after migration to TF 2.x):python
import numpy as np
import tensorflow as tf
tf.compat.v1.placeholder with default(input=np.array([2]),shape=tf.constant(dtype=tf.qint8, value=np.array([1])))In these scenarios, since the kernel is missing, a [
nullptr value is passed](https://github.com/tensorflow/tensorflow/blob/f3b9bf4c3c0597563b289c0512e98d4ce81f886e/tensorflow/python/eager/pywrap tfe src.cc#L480-L482) to [ParseDimensionValue](https://github.com/tensorflow/tensorflow/blob/f3b9bf4c3c0597563b289c0512e98d4ce81f886e/tensorflow/python/eager/pywrap tfe src.cc#L296-L320) for the py value argument. Then, this is dereferenced, resulting in segfault.Patches
We have patched the issue in GitHub commit 237822b59fc504dda2c564787f5d3ad9c4aa62d9.
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 Hong Jin from Singapore Management University.
Fix
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Tensorflow-Cpu