CVE-2022-23590

Crash due to erroneous `StatusOr` in Tensorflow

5.9 MediumFix available

Tensorflow is an Open Source Machine Learning Framework. A GraphDef from a TensorFlow SavedModel can be maliciously altered to cause a TensorFlow process to crash due to encountering a StatusOr value that is an error and forcibly extracting the value from it. We have patched the issue in multiple GitHub commits and these will be included in TensorFlow 2.8.0 and TensorFlow 2.7.1, as both are affected.

Attack profile

How easy it is to exploit

Attack vector: Network
Complexity: High
Privileges needed: None
User interaction: None

What an attacker can affect

Confidentiality: None
Integrity: None
Availability: High

Exploit likelihood

0.98%Up 0.1 points since Feb 8, 2022

What each source reports

CVE List Score used 5.9

Crash due to erroneous `StatusOr` in Tensorflow

Record: CVE-2022-23590
CVSS 3.1: 5.9 MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness: CWE-754
Updated: 2026-11-02

EUVDEUVD-2022-0338 5.9

Record: EUVD-2022-0338
CVSS 3.1: 5.9 MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Updated: 2026-11-02

GitHub AdvisoriesGHSA-pqrv-8r2f-7278 5.9

Crash due to erroneous `StatusOr` in TensorFlow

Impact

A GraphDef from a TensorFlow SavedModel can be maliciously altered to cause a TensorFlow process to crash due to encountering a StatusOr value that is an error and forcibly extracting the value from it:

  if (op_reg_data->type_ctor != nullptr) {
    VLOG(3) << "AddNode: found type constructor for " << node_def.name();
    const auto ctor_type =
        full_type::SpecializeType(AttrSlice(node_def), op_reg_data->op_def);
    const FullTypeDef ctor_typedef = ctor_type.ValueOrDie();
    if (ctor_typedef.type_id() != TFT_UNSET) {
      *(node_def.mutable_experimental_type()) = ctor_typedef;
    }
  }

If ctor_type is an error status, ValueOrDie results in a crash.

Patches

We have patched the issue in GitHub commit 955059813cc325dc1db5e2daa6221271406d4439.

We have patched the issue in multiple GitHub commits and these will be included in TensorFlow 2.8.0 and TensorFlow 2.7.1, as both are affected.

For more information

Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Record: GHSA-pqrv-8r2f-7278
CVSS 3.1: 5.9 MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness: CWE-754
Updated: 2026-11-02

NVD 5.9

Record: CVE-2022-23590
CVSS 3.1: 5.9 MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 3.1: 7.5 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.0: 5.0 MediumAV:N/AC:L/Au:N/C:N/I:N/A:P
Weakness: CWE-754
Updated: 2026-11-02

OSV 5.9

Crash due to erroneous `StatusOr` in Tensorflow

Record: CVE-2022-23590
CVSS 3.1: 5.9 MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness: CWE-754
Updated: 2026-11-02

OSVGHSA-pqrv-8r2f-7278 5.9

Crash due to erroneous `StatusOr` in TensorFlow

Impact

  if (op_reg_data->type_ctor != nullptr) {
    VLOG(3) << "AddNode: found type constructor for " << node_def.name();
    const auto ctor_type =
        full_type::SpecializeType(AttrSlice(node_def), op_reg_data->op_def);
    const FullTypeDef ctor_typedef = ctor_type.ValueOrDie();
    if (ctor_typedef.type_id() != TFT_UNSET) {
      *(node_def.mutable_experimental_type()) = ctor_typedef;
    }
  }

If ctor_type is an error status, ValueOrDie results in a crash.

Patches

We have patched the issue in GitHub commit 955059813cc325dc1db5e2daa6221271406d4439.

We have patched the issue in multiple GitHub commits and these will be included in TensorFlow 2.8.0 and TensorFlow 2.7.1, as both are affected.

For more information

Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Record: GHSA-pqrv-8r2f-7278
CVSS 3.1: 5.9 MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness: CWE-754
Updated: 2026-11-02

Show 5 moreShow less

OSVPYSEC-2026-3225 5.9

Crash due to erroneous `StatusOr` in TensorFlow

Impact

  if (op_reg_data->type_ctor != nullptr) {
    VLOG(3) << "AddNode: found type constructor for " << node_def.name();
    const auto ctor_type =
        full_type::SpecializeType(AttrSlice(node_def), op_reg_data->op_def);
    const FullTypeDef ctor_typedef = ctor_type.ValueOrDie();
    if (ctor_typedef.type_id() != TFT_UNSET) {
      *(node_def.mutable_experimental_type()) = ctor_typedef;
    }
  }

If ctor_type is an error status, ValueOrDie results in a crash.

Patches

We have patched the issue in GitHub commit 955059813cc325dc1db5e2daa6221271406d4439.

We have patched the issue in multiple GitHub commits and these will be included in TensorFlow 2.8.0 and TensorFlow 2.7.1, as both are affected.

For more information

Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Record: PYSEC-2026-3225
CVSS 3.1: 5.9 MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Updated: 2026-11-02

OSVBIT-tensorflow-2022-23590 No score

Crash due to erroneous `StatusOr` in Tensorflow

Record: BIT-tensorflow-2022-23590
Updated: 2026-11-02

OSVopenSUSE-SU-2024:12116-1 No score

tensorflow-lite-2.9.1-1.1 on GA media

These are all security issues fixed in the tensorflow-lite-2.9.1-1.1 package on the GA media of openSUSE Tumbleweed.

Record: openSUSE-SU-2024:12116-1
Updated: 2026-11-02

OSVPYSEC-2022-154 No score

Record: PYSEC-2022-154
Updated: 2026-11-02

OSVPYSEC-2022-99 No score

Record: PYSEC-2022-99
Updated: 2026-11-02

Affected products

Affected packages

Affected packages
Package	Affected	Fixed
`tensorflow` PyPI	before 2.7.1	2.7.1
`tensorflow-cpu` PyPI	before 2.7.1	2.7.1
`tensorflow-gpu` PyPI	before 2.7.1	2.7.1
`tensorflow` Bitnami	before 2.7.1	2.7.1
`tensorflow` PyPI	before 2.7.1, plus listed versions 0.12.00.12.11.0.01.0.11.1.0 Show 45 moreShow less 1.10.01.10.11.11.01.12.01.12.21.12.31.13.11.13.21.14.01.15.01.15.21.15.31.15.41.15.51.2.01.2.11.3.01.4.01.4.11.5.01.5.11.6.01.7.01.7.11.8.01.9.02.0.02.0.12.0.22.0.32.0.42.1.02.1.12.1.22.1.32.1.42.2.02.2.12.2.22.2.32.3.02.3.12.3.22.3.32.3.4	2.7.1
`tensorflow-cpu` PyPI	before 2.7.1, plus listed versions 1.15.02.1.02.1.12.1.22.1.3 Show 26 moreShow less 2.1.42.2.02.2.12.2.22.2.32.3.02.3.12.3.22.3.32.3.42.4.02.4.12.4.22.4.32.4.42.5.02.5.12.5.22.5.32.6.02.6.12.6.22.6.32.6.42.6.52.7.0	2.7.1
`tensorflow-gpu` PyPI	before 2.7.1, plus listed versions 0.12.00.12.11.0.01.0.11.1.0 Show 45 moreShow less 1.10.01.10.11.11.01.12.01.12.21.12.31.13.11.13.21.14.01.15.01.15.21.15.31.15.41.15.51.2.01.2.11.3.01.4.01.4.11.5.01.5.11.6.01.7.01.7.11.8.01.9.02.0.02.0.12.0.22.0.32.0.42.1.02.1.12.1.22.1.32.1.42.2.02.2.12.2.22.2.32.3.02.3.12.3.22.3.32.3.4	2.7.1
`tensorflow-gpu` PyPI	before 2.7.1, plus listed versions 0.12.00.12.11.0.01.0.11.1.0 Show 45 moreShow less 1.10.01.10.11.11.01.12.01.12.21.12.31.13.11.13.21.14.01.15.01.15.21.15.31.15.41.15.51.2.01.2.11.3.01.4.01.4.11.5.01.5.11.6.01.7.01.7.11.8.01.9.02.0.02.0.12.0.22.0.32.0.42.1.02.1.12.1.22.1.32.1.42.2.02.2.12.2.22.2.32.3.02.3.12.3.22.3.32.3.4	2.7.1
`tensorflow-cpu` PyPI	before 2.7.1, plus listed versions 1.15.02.1.02.1.12.1.22.1.3 Show 28 moreShow less 2.1.42.2.02.2.12.2.22.2.32.3.02.3.12.3.22.3.32.3.42.4.02.4.12.4.22.4.32.4.42.5.02.5.12.5.22.5.32.6.02.6.12.6.22.6.32.7.02.7.0rc02.7.0rc12.6.42.6.5	2.7.1

History

History
Recorded	Changed	Sources
Nov 6, 2026	facts
Nov 2, 2026	first indexed	CVE List, EUVD, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2022-23590 is a medium vulnerability (CVSS 5.9) in Google Tensorflow, published February 4, 2022. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.98%, the 62nd percentile. Fixed in tensorflow 2.7.1.

References

Show 167 moreShow less

This page doesn't list everything

Left out here: 57 versions. The JSON record has them.