TensorFlow has Null Pointer Error in SparseSparseMaximum (CVE-2023-25665) | HOL Guard CVE

High · CVSS 7.5CVE-2023-25665GHSA-558H-MQ8X-7Q9G

TensorFlow has Null Pointer Error in SparseSparseMaximum

Answer in brief

CVE-2023-25665 records a High severity (CVSS 7.5) vulnerability in TensorFlow has Null Pointer Error in SparseSparseMaximum. 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.

Published Mar 24, 2023Updated Sep 10, 2026Source checked Sep 10, 2026First seen by HOL Sep 10, 2026Material review Sep 10, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.5
Exploitation: Not marked as known exploited
Affected software: 3 mapped packages or products
Fix availability: Available

Why this deserves its current priority

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.

Affected scope and exposure questions

The current feed maps tensorflow (pypi), tensorflow-cpu (pypi), tensorflow-gpu (pypi). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
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

Recommended response

Check inventory. Check lockfiles and deployed manifests for tensorflow, tensorflow-cpu, tensorflow-gpu.
Review the reported fix. Update tensorflow to 2.11.1; tensorflow-cpu to 2.11.1; tensorflow-gpu to 2.11.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Mar 24, 2023
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Sep 10, 2026

Sources and claim methodology

Upstream source description

### Impact When `SparseSparseMaximum` is given invalid sparse tensors as inputs, it can give an NPE. ```python import tensorflow as tf tf.raw_ops.SparseSparseMaximum( a_indices=[[1]], a_values =[ 0.1 ], a_shape = [2], b_indices=[[]], b_values =[2 ], b_shape = [2], ) ``` ### Patches We have patched the issue in GitHub commit [5e0ecfb42f5f65629fd7a4edd6c4afe7ff0feb04](https://github.com/tensorflow/tensorflow/commit/5e0ecfb42f5f65629fd7a4edd6c4afe7ff0feb04). 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 Yu Tian of Qihoo 360 AIVul Team

Quoted source text, attributed separately from HOL analysis.