GHSA-m9g8-fxxm-xg86 — django
CRITICALGHSA-m9g8-fxxm-xg86 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in django. A fix is available for django — see the affected versions and patch details below.
Django SQL injection in HasKey(lhs, rhs) on Oracle
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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 GHSA-m9g8-fxxm-xg86.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-m9g8-fxxm-xg86 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
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.10pip install --upgrade 'django==5.0.10' |
| 🐍PyPI | django | ≥ 5.1.0&&< 5.1.4 | 5.1.4pip install --upgrade 'django==5.1.4' |
| 🐍PyPI | django | ≥ 4.2.0&&< 4.2.17 | 4.2.17pip install --upgrade 'django==4.2.17' |
| 🐍PyPI | django | ≥ 5.1&&< 5.1.4 | 5.1.4pip install --upgrade 'django==5.1.4' |
| 🐍PyPI | django | ≥ 5.0&&< 5.0.10 | 5.0.10pip install --upgrade 'django==5.0.10' |
| 🐍PyPI | django | ≥ 4.2&&< 4.2.17 | 4.2.17pip install --upgrade 'django==4.2.17' |
Affected Products
djangodjangoprojectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Ansible Automation Platform 2.4 for RHEL 8 | ansible-automation-platform-24/aap-cloud-billing-rhel8:0.3.0-51 | RHSA-2024:11144 |
| Red Hat Ansible Automation Platform 2.4 for RHEL 8 | automation-controller-0:4.5.17-1.el8ap | RHSA-2025:0721 |
| Red Hat Ansible Automation Platform 2.5 for RHEL 8 | ansible-automation-platform-25/aap-cloud-billing-rhel8:0.3.0-54 | RHSA-2024:11146 |
| Red Hat Ansible Automation Platform 2.5 for RHEL 8 | automation-controller-0:4.6.6-1.el8ap | RHSA-2025:0340 |
Frequently Asked Questions
Is GHSA-m9g8-fxxm-xg86 in your dependencies?
Find it across PyPI, including transitive dependencies.