Skip to content
Fencer Vulns
high 8.8

CVE-2022-23594 json

Out of bounds read in Tensorflow

published 2022-02-04 4 y ago modified 2026-09-10 59 d ago also BIT-tensorflow-2022-23594 , EUVD-2022-0947 , GHSA-9x52-887g-fhc2 , PYSEC-2026-3157 , PYSEC-2026-3309 , PYSEC-2026-752

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

Summary

Tensorflow is an Open Source Machine Learning Framework. The TFG dialect of TensorFlow (MLIR) makes several assumptions about the incoming `GraphDef` before converting it to the MLIR-based dialect. If an attacker changes the `SavedModel` format on disk to invalidate these assumptions and the `GraphDef` is then converted to MLIR-based IR then they can cause a crash in the Python interpreter. Under certain scenarios, heap OOB read/writes are possible. These issues have been discovered via fuzzing and it is possible that more weaknesses exist. We will patch them as they are discovered.

Patch / fix

  • pypi tensorflow 2.7.1
  • pypi tensorflow-cpu 2.7.1
  • pypi tensorflow-gpu 2.7.1
  • bitnami tensorflow 2.7.1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
18 mo ago

Exploit prediction

0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 8.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 8.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:N/I:N/A:P
OSV 3.1 8.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi tensorflow
>=2.7.0, <2.7.1
2.7.1
pypi tensorflow-cpu
>=2.7.0, <2.7.1
2.7.1
pypi tensorflow-gpu
>=2.7.0, <2.7.1
2.7.1
bitnami tensorflow
>=2.7.0, <2.7.1
2.7.1

Affected products

  • tensorflow tensorflow

Classification

Weakness

References

Sources

Fencer Vulns 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.