Skip to content
Fencer Vulns
high 7.5

CVE-2023-27579 json

TensorFlow has Floating Point Exception in TFLite in conv kernel

published 2023-03-24 3 y ago modified 2026-09-10 1 mo ago also BIT-tensorflow-2023-27579 , EUVD-2023-0889 , GHSA-5w96-866f-6rm8 , PYSEC-2026-3111 , PYSEC-2026-3279 , PYSEC-2026-954

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

Summary

TensorFlow is an end-to-end open source platform for machine learning. Constructing a tflite model with a paramater `filter_input_channel` of less than 1 gives a FPE. This issue has been patched in version 2.12. TensorFlow will also cherrypick the fix commit on TensorFlow 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-31208AZL-35323

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

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
20 mo ago

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 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.