How severe is GHSA-5889-7v45-q28m?

GHSA-5889-7v45-q28m has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-5889-7v45-q28m?

GHSA-5889-7v45-q28m 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 GHSA-5889-7v45-q28m?

Update tensorflow to 2.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5889-7v45-q28m is resolved across your whole dependency graph.

How do I detect GHSA-5889-7v45-q28m 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 GHSA-5889-7v45-q28m 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 GHSA-5889-7v45-q28m actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-5889-7v45-q28m, including 2 in-the-wild exploitations 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 GHSA-5889-7v45-q28m?

GHSA-5889-7v45-q28m has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 25th 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 GHSA-5889-7v45-q28m?

GHSA-5889-7v45-q28m 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 GHSA-5889-7v45-q28m published, and has it been updated?

GHSA-5889-7v45-q28m was published on May 24, 2022 and was last updated on July 13, 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

Incomplete validation in signal ops leads to crashes in TensorFlowGHSA-5889-7v45-q28m

MEDIUMFix: tensorflow/tensorflow#55274

GHSA-5889-7v45-q28m is a medium-severity (CVSS 5.5) Improper Input Validation vulnerability in tensorflow. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for tensorflow — see the affected versions and patch details below.

Also known asBIT-tensorflow-2022-29213CVE-2022-29213PYSEC-2026-3107PYSEC-2026-3277PYSEC-2026-952

Published

May 24, 2022

Updated

Jul 13, 2026

Affected

9 pkgs

Patched

9 / 9

Exploits

2 known

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-5889-7v45-q28m.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs25th percentile — riskier than 25% 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-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 tf.compat.v1.signal.rfft2d and tf.compat.v1.signal.rfft3d lack input validation and under certain condition can result in crashes (due to CHECK-failures).

Patches

We have patched the issue in GitHub commit 0a8a781e597b18ead006d19b7d23d0a369e9ad73 (merging GitHub PR #55274).

The fix will be included in TensorFlow 2.9.0. We will also cherrypick this commit on TensorFlow 2.8.1, TensorFlow 2.7.2, and TensorFlow 2.6.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 externally via a GitHub issue.

Affected Packages

9 total 9 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`tensorflow`	all versions	2.6.4`pip install --upgrade 'tensorflow==2.6.4'`
🐍PyPI	`tensorflow`	≥ 2.7.0&&< 2.7.2	2.7.2`pip install --upgrade 'tensorflow==2.7.2'`
🐍PyPI	`tensorflow`	≥ 2.8.0&&< 2.8.1	2.8.1`pip install --upgrade 'tensorflow==2.8.1'`
🐍PyPI	`tensorflow-cpu`	all versions	2.6.4`pip install --upgrade 'tensorflow-cpu==2.6.4'`
🐍PyPI	`tensorflow-cpu`	≥ 2.7.0&&< 2.7.2	2.7.2`pip install --upgrade 'tensorflow-cpu==2.7.2'`
🐍PyPI	`tensorflow-cpu`	≥ 2.8.0&&< 2.8.1	2.8.1`pip install --upgrade 'tensorflow-cpu==2.8.1'`

Affected Products

1 product · 9 configurations

Application

tensorflowgoogle

≥ 2.7.0 && < 2.7.2

3 versions

2.7.02.8.02.9.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 platform for machine learning. Prior to ver…

github.comNVDJun 2022

Report on github.com

github.comNVDJun 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.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5889-7v45-q28m 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 The `tf.compat.v1.signal.rfft2d` and `tf.compat.v1.signal.rfft3d` lack input validation and under certain condition can result in crashes (due to `CHECK`-failures). ### Patches We have patched the issue in GitHub commit [0a8a781e597b18ead006d19b7d23d0a369e9ad73](https://github.com/tensorflow/tensorflow/commit/0a8a781e597b18ead006d19b7d23d0a369e9ad73) (merging GitHub PR [#55274](https://github.com/tensorflow/tensorflow/pull/55274)). The fix will be included in TensorFlow 2.9.0. We will also cherrypick this commit on TensorFlow 2.8.1, TensorFlow 2.7.2, and TensorFlow 2.6.4, as thes

O3 Security · Impact-Aware SCA

Is GHSA-5889-7v45-q28m in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.5/10CVSS v3 base

Vector breakdown

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Raw vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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. 2 public proof-of-concept references are listed on this page.

OpenSSF Scorecard

Package health score

tensorflow

7.9/10

Maintained10/10

Code-Review7/10

Dependency-Update-Tool10/10

Branch-ProtectionN/A

Vulnerabilities0/10

Assessed Nov 6, 2026

Timeline

Disclosed

May 24, 2022

First exploit

Jun 7, 2022

Last updated

Jul 13, 2026

Identifiers

GHSA-5889-7v45-q28m

BIT-tensorflow-2022-29213

PYSEC-2026-3107

PYSEC-2026-3277

References

Advisorynvd.nist.gov · CVE 2022 29213 Webgithub.com · GHSA 5889 7v45 q28m Webgithub.com Webgithub.com Webgithub.com · 0a8a781e597b18ead006d19b7d23d0a369e9ad73 Webgithub.com · v2.6.4 Webgithub.com · v2.7.2 Webgithub.com · v2.8.1 Webgithub.com · v2.9.0 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 verifiedJul 13, 2026

Incomplete validation in signal ops leads to crashes in TensorFlowGHSA-5889-7v45-q28m

Exploitation Status

Proof-of-concept exploit code exists

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 GHSA-5889-7v45-q28m in your dependencies?