How severe is CVE-2022-41901?

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

Which packages are affected by CVE-2022-41901?

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

How do I fix CVE-2022-41901?

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

How do I detect CVE-2022-41901 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-41901 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

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

Yes. There are 1 known exploit references for CVE-2022-41901, 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-41901?

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

CVE-2022-41901 is classified as Improper Input Validation (CWE-20), Reachable Assertion (CWE-617). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2022-41901 was published on November 18, 2022 and was last updated on October 28, 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-41901 — tensorflow

MEDIUMFix: tensorflow/tensorflow@f856d02

CVE-2022-41901 is a medium-severity (CVSS 4.8) Improper Input Validation vulnerability in tensorflow. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for tensorflow — see the affected versions and patch details below.

`CHECK_EQ` fail via input in `SparseMatrixNNZ` in Tensorflow

Also known asBIT-tensorflow-2022-41901GHSA-g9fm-r5mm-rf9fPYSEC-2026-3185PYSEC-2026-3328PYSEC-2026-997

Published

Nov 18, 2022

Updated

Oct 28, 2026

Affected

9 pkgs

Patched

9 / 9

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk+0.02%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

9 pkgs affected

🐍tensorflow🐍tensorflow🐍tensorflow🐍tensorflow-cpu🐍tensorflow-gpu🐍tensorflow-cpu🐍tensorflow-gpu🐍tensorflow-cpu+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

An input sparse_matrix that is not a matrix with a shape with rank 0 will trigger a CHECK fail in tf.raw_ops.SparseMatrixNNZ.

import tensorflow as tf
tf.raw_ops.SparseMatrixNNZ(sparse_matrix=[])

Patches

We have patched the issue in GitHub commit f856d02e5322821aad155dad9b3acab1e9f5d693.

The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, 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 Kang Hong Jin

Affected Packages

9 total 9 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`tensorflow`	all versions	2.8.4`pip install --upgrade 'tensorflow==2.8.4'`
🐍PyPI	`tensorflow`	≥ 2.9.0&&< 2.9.3	2.9.3`pip install --upgrade 'tensorflow==2.9.3'`
🐍PyPI	`tensorflow`	≥ 2.10.0&&< 2.10.1	2.10.1`pip install --upgrade 'tensorflow==2.10.1'`
🐍PyPI	`tensorflow-cpu`	all versions	2.8.4`pip install --upgrade 'tensorflow-cpu==2.8.4'`
🐍PyPI	`tensorflow-gpu`	all versions	2.8.4`pip install --upgrade 'tensorflow-gpu==2.8.4'`
🐍PyPI	`tensorflow-cpu`	≥ 2.9.0&&< 2.9.3	2.9.3`pip install --upgrade 'tensorflow-cpu==2.9.3'`

Affected Products

1 product · 3 configurations

Application

tensorflowgoogle

≥ 2.10.0 && < 2.10.1

range

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 platform for machine learning. An input `sp…

github.comNVDNov 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.8.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-41901 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact An input `sparse_matrix` that is not a matrix with a shape with rank 0 will trigger a `CHECK` fail in [`tf.raw_ops.SparseMatrixNNZ`](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/kernels/sparse/sparse_matrix.h). ```python import tensorflow as tf tf.raw_ops.SparseMatrixNNZ(sparse_matrix=[]) ``` ### Patches We have patched the issue in GitHub commit [f856d02e5322821aad155dad9b3acab1e9f5d693](https://github.com/tensorflow/tensorflow/commit/f856d02e5322821aad155dad9b3acab1e9f5d693). The fix will be included in TensorFlow 2.11. We will also cherrypick this commi

O3 Security · Impact-Aware SCA

Is CVE-2022-41901 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Raw vector

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

CWE Classification

CWE-20Improper Input Validation CWE-617Reachable Assertion

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

tensorflow

7.7/10

Dependency-Update-Tool10/10

Maintained10/10

Code-Review7/10

Branch-ProtectionN/A

Vulnerabilities0/10

Assessed Oct 31, 2026

Timeline

Disclosed

Nov 18, 2022

First exploit

Nov 23, 2022

6 days after disclosure — rapid exploitation

Last updated

Oct 28, 2026

Identifiers

CVE-2022-41901

GHSA-g9fm-r5mm-rf9f

BIT-tensorflow-2022-41901

PYSEC-2026-3185

PYSEC-2026-3328

References

Advisorygithub.com · CVE 2022 41901.json Advisorygithub.com · GHSA g9fm r5mm rf9f Advisorynvd.nist.gov · CVE 2022 41901 Fixgithub.com · f856d02e5322821aad155dad9b3acab1e9f5d693 Webgithub.com · sparse matrix.h Packagegithub.com · tensorflow

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 verifiedOct 28, 2026