Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
CRITICAL severity

GHSA-2gwj-7jmv-h26r django

CRITICALFix: django/django@2044dac

GHSA-2gwj-7jmv-h26r is a critical-severity (CVSS 9.8) SQL Injection vulnerability in django. 3 public exploit references exist, so weaponization risk is real. A fix is available for django — see the affected versions and patch details below.

SQL Injection in Django

Also known asBIT-django-2022-28346CVE-2022-28346PYSEC-2022-190
Published
Apr 13, 2022
Updated
Feb 21, 2025
Affected
3 pkgs
Patched
3 / 3
Exploits
3 known
Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
18.7%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-2gwj-7jmv-h26r plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,166 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

3 pkgs affected
🐍django🐍django🐍django

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

An issue was discovered in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0 before 4.0.4. QuerySet.annotate(), aggregate(), and extra() methods are subject to SQL injection in column aliases via a crafted dictionary (with dictionary expansion) as the passed **kwargs.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIdjango2.2&&< 2.2.282.2.28pip install --upgrade 'django==2.2.28'
🐍PyPIdjango3.2&&< 3.2.133.2.13pip install --upgrade 'django==3.2.13'
🐍PyPIdjango4.0&&< 4.0.44.0.4pip install --upgrade 'django==4.0.4'
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    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.

  2. Fix

    Update django to 2.2.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2gwj-7jmv-h26r is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2gwj-7jmv-h26r can be triaged on real exposure rather than presence alone.

Tailored to GHSA-2gwj-7jmv-h26r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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.

Red HatImportant

Red Hat OpenStack does ship the affected version of Django, however, vulnerability is not exposed in the product as it does not make use of vulnerable code. We may update Django in a future release of OpenStack.

ProductFixed inAdvisory
Red Hat Ansible Automation Platform 2.1 for RHEL 8automation-controller-0:4.1.2-2.el8apRHSA-2022:5702
Red Hat Automation Hub 4.2 for RHEL 7python3-django-0:2.2.28-1.el7pcRHSA-2022:5703
Red Hat OpenStack Platform 16.1python-django20-0:2.0.13-18.el8ostRHSA-2022:8872
Red Hat OpenStack Platform 16.2python-django20-0:2.0.13-17.el8ostRHSA-2022:5115
Red Hat Satellite 6.11 for RHEL 8python-django-0:3.2.13-1.el8pcRHSA-2022:5498
RHUI 4 for RHEL 8python-django-0:3.2.13-2.el8uiRHSA-2022:5602

Frequently Asked Questions

An issue was discovered in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0 before 4.0.4. `QuerySet.annotate()`, `aggregate()`, and `extra()` methods are subject to SQL injection in column aliases via a crafted dictionary (with dictionary expansion) as the passed `**kwargs`.
O3 Security · Impact-Aware SCA

Is GHSA-2gwj-7jmv-h26r in your dependencies?

O3 Security finds GHSA-2gwj-7jmv-h26r across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-2gwj-7jmv-h26r: django (Critical 9.8) | O3 Security