How severe is CVE-2022-23581?

CVE-2022-23581 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-23581?

CVE-2022-23581 affects the following packages: tensorflow (PyPI), tensorflow (PyPI), tensorflow (PyPI), tensorflow-cpu (PyPI), tensorflow-cpu (PyPI), tensorflow-cpu (PyPI), tensorflow-gpu (PyPI), tensorflow-gpu (PyPI), and 1 more. Ecosystems affected: PyPI.

How do I fix CVE-2022-23581?

Update tensorflow to 2.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23581 is resolved across your whole dependency graph.

How do I detect CVE-2022-23581 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tensorflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-23581 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2022-23581 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-23581, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-23581?

CVE-2022-23581 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 66th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-23581?

CVE-2022-23581 is classified as Reachable Assertion (CWE-617). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-23581 published, and has it been updated?

CVE-2022-23581 was published on February 4, 2022 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

CVE-2022-23581 — tensorflow

MEDIUMFix: tensorflow/tensorflow@1fb2773

CVE-2022-23581 is a medium-severity (CVSS 6.5) Reachable Assertion vulnerability in tensorflow. 1 public exploit reference exists, so weaponization risk is real. A fix is available for tensorflow — see the affected versions and patch details below.

`CHECK`-failures during Grappler's `IsSimplifiableReshape` in Tensorflow

Also known asBIT-tensorflow-2022-23581GHSA-fq86-3f29-px2cPYSEC-2022-145PYSEC-2022-90PYSEC-2026-3175

Published

Feb 4, 2022

Updated

Aug 12, 2026

Affected

9 pkgs

Patched

9 / 9

Exploits

1 known

Exploitation data as of Oct 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs66th percentile — riskier than 66% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2022-23581 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

9 pkgs affected

🐍tensorflow🐍tensorflow🐍tensorflow🐍tensorflow-cpu🐍tensorflow-cpu🐍tensorflow-cpu🐍tensorflow-gpu🐍tensorflow-gpu+1 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The Grappler optimizer in TensorFlow can be used to cause a denial of service by altering a SavedModel such that IsSimplifiableReshape would trigger CHECK failures.

Patches

We have patched the issue in GitHub commits ebc1a2ffe5a7573d905e99bd0ee3568ee07c12c1, 1fb27733f943295d874417630edd3b38b34ce082, and 240655511cd3e701155f944a972db71b6c0b1bb6.

The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.

For more information

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

Affected Packages

9 total 9 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`tensorflow`	all versions	2.5.3`pip install --upgrade 'tensorflow==2.5.3'`
🐍PyPI	`tensorflow`	≥ 2.6.0&&< 2.6.3	2.6.3`pip install --upgrade 'tensorflow==2.6.3'`
🐍PyPI	`tensorflow`	≥ 2.7.0&&< 2.7.1	2.7.1`pip install --upgrade 'tensorflow==2.7.1'`
🐍PyPI	`tensorflow-cpu`	all versions	2.5.3`pip install --upgrade 'tensorflow-cpu==2.5.3'`
🐍PyPI	`tensorflow-cpu`	≥ 2.6.0&&< 2.6.3	2.6.3`pip install --upgrade 'tensorflow-cpu==2.6.3'`
🐍PyPI	`tensorflow-cpu`	≥ 2.7.0&&< 2.7.1	2.7.1`pip install --upgrade 'tensorflow-cpu==2.7.1'`

Affected Products

1 product · 3 configurations

Application

tensorflowgoogle

≥ 2.6.0 && ≤ 2.6.2

1 version

2.7.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Tensorflow is an Open Source Machine Learning Framework. The Grappler op…

github.comNVDFeb 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tensorflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tensorflow to 2.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23581 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### Impact The Grappler optimizer in TensorFlow can be used to cause a denial of service by altering a `SavedModel` such that [`IsSimplifiableReshape`](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/grappler/optimizers/constant_folding.cc#L1687-L1742) would trigger `CHECK` failures. ### Patches We have patched the issue in GitHub commits [ebc1a2ffe5a7573d905e99bd0ee3568ee07c12c1](https://github.com/tensorflow/tensorflow/commit/ebc1a2ffe5a7573d905e99bd0ee3568ee07c12c1), [1fb27733f943295d874417630edd3b38b34ce082](https://github.com/tensorf

O3 Security · Impact-Aware SCA

Is CVE-2022-23581 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CWE Classification

CWE-617Reachable Assertion

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

tensorflow

7.7/10

Maintained10/10

Code-Review7/10

Dependency-Update-Tool10/10

Branch-ProtectionN/A

Vulnerabilities0/10

Assessed Oct 1, 2026

Timeline

Disclosed

Feb 4, 2022

First exploit

Feb 10, 2022

5 days after disclosure — rapid exploitation

Last updated

Aug 12, 2026

Identifiers

CVE-2022-23581

GHSA-fq86-3f29-px2c

BIT-tensorflow-2022-23581

PYSEC-2022-145

PYSEC-2022-90

References

Advisorygithub.com Advisorygithub.com Advisorynvd.nist.gov Fixgithub.com Fixgithub.com Fixgithub.com Webgithub.com Webgithub.com Webgithub.com Webgithub.com

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting tensorflow are rated as high or higher (top: high).

CVE-2023-33976CVE-2023-25661CVE-2023-25670CVE-2023-25665CVE-2023-27579CVE-2023-25673CVE-2023-25663CVE-2023-25658

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedAug 12, 2026

CVE-2022-23581 — tensorflow

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Impact

Patches

For more information

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-23581 in your dependencies?