GHSA-qx3f-p745-w4hr is a high-severity (CVSS 7.6) CWE-190 vulnerability in tensorflow. O3 Security confirms whether GHSA-qx3f-p745-w4hr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Integer overflow in Tensorflow
Real-World Exposure
tensorflow🐍tensorflow🐍tensorflow🐍tensorflow-cpu🐍tensorflow-cpu🐍tensorflow-cpu🐍tensorflow-gpu🐍tensorflow-gpu+1 moreReal-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 implementation of Range suffers from integer overflows. These can trigger undefined behavior or, in some scenarios, extremely large allocations.
Patches
We have patched the issue in GitHub commit f0147751fd5d2ff23251149ebad9af9f03010732 (merging #51733).
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 externally via a GitHub issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | tensorflow | all versions | 2.5.3 |
| 🐍PyPI | tensorflow | ≥ 2.6.0&&< 2.6.3 | 2.6.3 |
| 🐍PyPI | tensorflow | ≥ 2.7.0&&< 2.7.1 | 2.7.1 |
| 🐍PyPI | tensorflow-cpu | all versions | 2.5.3 |
| 🐍PyPI | tensorflow-cpu | ≥ 2.6.0&&< 2.6.3 | 2.6.3 |
| 🐍PyPI | tensorflow-cpu | ≥ 2.7.0&&< 2.7.1 | 2.7.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tensorflow. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update tensorflow to 2.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qx3f-p745-w4hr 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.
How O3 protects you
O3 pinpoints whether GHSA-qx3f-p745-w4hr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-qx3f-p745-w4hr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-qx3f-p745-w4hr in your dependencies?
O3 detects GHSA-qx3f-p745-w4hr across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.