How severe is CVE-2022-23569?

CVE-2022-23569 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-23569?

CVE-2022-23569 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-23569?

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

How do I detect CVE-2022-23569 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-23569 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-23569 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-23569 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

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

CVE-2022-23569 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 38th 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-23569?

CVE-2022-23569 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-23569 published, and has it been updated?

CVE-2022-23569 was published on February 3, 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-23569 — tensorflow

MEDIUM

CVE-2022-23569 is a medium-severity (CVSS 6.5) Reachable Assertion vulnerability in tensorflow. A fix is available for tensorflow — see the affected versions and patch details below.

`CHECK`-fails when building invalid tensor shapes in Tensorflow

Also known asBIT-tensorflow-2022-23569GHSA-qj5r-f9mv-rffhPYSEC-2022-133PYSEC-2022-78PYSEC-2026-3230

Published

Feb 3, 2022

Updated

Aug 12, 2026

Affected

9 pkgs

Patched

9 / 9

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-23569.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk+0.00%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2022-23569 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

Multiple operations in TensorFlow can be used to trigger a denial of service via CHECK-fails (i.e., assertion failures). This is similar to TFSA-2021-198 (CVE-2021-41197) and has similar fixes.

Patches

We have patched the reported issues in multiple GitHub commits. It is possible that other similar instances exist in TensorFlow, we will issue fixes as these are discovered.

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.

Attribution

This vulnerability has been reported by Faysal Hossain Shezan from University of Virginia.

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

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-23569 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 Multiple operations in TensorFlow can be used to trigger a denial of service via `CHECK`-fails (i.e., assertion failures). This is similar to [TFSA-2021-198](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-198.md) (CVE-2021-41197) and has similar fixes. ### Patches We have patched the reported issues in multiple GitHub commits. It is possible that other similar instances exist in TensorFlow, we will issue fixes as these are discovered. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1,

O3 Security · Impact-Aware SCA

Is CVE-2022-23569 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.

Timeline

Disclosed

Feb 3, 2022

Last updated

Aug 12, 2026

Identifiers

CVE-2022-23569

GHSA-qj5r-f9mv-rffh

BIT-tensorflow-2022-23569

PYSEC-2022-133

PYSEC-2022-78

References

Advisorygithub.com Advisorygithub.com Advisorygithub.com Advisorynvd.nist.gov Webgithub.com Webgithub.com Packagegithub.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-23569 — tensorflow

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Impact

Patches

For more information

Attribution

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-23569 in your dependencies?