Skip to content
Fencer Intel
critical 9.8

CVE-2023-25668 json

TensorFlow vulnerable to heap out-of-buffer read in the QuantizeAndDequantize operation

published 3y ago modified 2mo ago also BIT-tensorflow-2023-25668 , EUVD-2023-1018 , GHSA-gw97-ff7c-9v96 , PYSEC-2026-548 , PYSEC-2026-549 , PYSEC-2026-550

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 58%
public exploits
0
none known

Summary

TensorFlow is an open source platform for machine learning. Attackers using Tensorflow prior to 2.12.0 or 2.11.1 can access heap memory which is not in the control of user, leading to a crash or remote code execution. The fix will be included in TensorFlow version 2.12.0 and will also cherrypick this commit on TensorFlow version 2.11.1.

Patch / fix

  • pypi tensorflow 2.11.1
  • pypi tensorflow-cpu 2.11.1
  • pypi tensorflow-gpu 2.11.1
  • bitnami tensorflow 2.12.0
  • google tensorflow 2.12.0
  • tensorflow CBL-Mariner 2.0, Azure Linux 3.0 2.11.1-1

azure linux advisories AZL-31200AZL-35313

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2023-25668 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
last yr.

Exploit prediction

0.84% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-15).

Exploits and checks

  • github.com https://github.com/tensorflow/tensorflow/commit/7b174a0f2e40ff3f3aa957aecddfd5aaae35eccb referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi tensorflow
<2.11.1
2.11.1
pypi tensorflow-cpu
<2.11.1
2.11.1
pypi tensorflow-gpu
<2.11.1
2.11.1
bitnami tensorflow
<2.12.0
2.12.0

Affected products

  • tensorflow tensorflow

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.