GHSA-m9g8-fxxm-xg86
CRITICALGHSA-m9g8-fxxm-xg86 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in django. O3 Security confirms whether GHSA-m9g8-fxxm-xg86 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Django SQL injection in HasKey(lhs, rhs) on Oracle
Real-World Exposure
django🐍django🐍django🐍django🐍django🐍djangoReal-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
An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. Direct usage of the django.db.models.fields.json.HasKey lookup, when an Oracle database is used, is subject to SQL injection if untrusted data is used as an lhs value. (Applications that use the jsonfield.has_key lookup via __ are unaffected.)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | django | ≥ 5.0.0&&< 5.0.10 | 5.0.10 |
| 🐍PyPI | django | ≥ 5.1.0&&< 5.1.4 | 5.1.4 |
| 🐍PyPI | django | ≥ 4.2.0&&< 4.2.17 | 4.2.17 |
| 🐍PyPI | django | ≥ 5.1&&< 5.1.4 | 5.1.4 |
| 🐍PyPI | django | ≥ 5.0&&< 5.0.10 | 5.0.10 |
| 🐍PyPI | django | ≥ 4.2&&< 4.2.17 | 4.2.17 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django. 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 django to 5.0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m9g8-fxxm-xg86 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-m9g8-fxxm-xg86 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-m9g8-fxxm-xg86. 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-m9g8-fxxm-xg86 in your dependencies?
O3 detects GHSA-m9g8-fxxm-xg86 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.