Answer in brief
CVE-2023-25675 records a High severity (CVSS 7.5) vulnerability in TensorFlow has Segfault in Bincount with XLA. The current sources do not mark it as known exploited. The current feed maps tensorflow (pypi), tensorflow-cpu (pypi), tensorflow-gpu (pypi). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps tensorflow (pypi), tensorflow-cpu (pypi), tensorflow-gpu (pypi). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| tensorflowpypi | >=0 <2.11.1 | 2.11.1 |
| tensorflow-cpupypi | >=0 <2.11.1 | 2.11.1 |
| tensorflow-gpupypi | >=0 <2.11.1 | 2.11.1 |
Published upstream
Mar 24, 2023
Evidence: source:osv:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Sep 10, 2026
### Impact When running with XLA, `tf.raw_ops.Bincount` segfaults when given a parameter `weights` that is neither the same shape as parameter `arr` nor a length-0 tensor. ```python import tensorflow as tf func = tf.raw_ops.Bincount para={'arr': 6, 'size': 804, 'weights': [52, 351]} @tf.function(jit_compile=True) def fuzz_jit(): y = func(**para) return y print(fuzz_jit()) ``` ### Patches We have patched the issue in GitHub commit [8ae76cf085f4be26295d2ecf2081e759e04b8acf](https://github.com/tensorflow/tensorflow/commit/8ae76cf085f4be26295d2ecf2081e759e04b8acf). The fix will be included in TensorFlow 2.12. We will also cherrypick this commit on TensorFlow 2.11.1. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. ### Attribution This vulnerability has been reported by r3pwnx of 360 AIVul Team
Quoted source text, attributed separately from HOL analysis.