NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

Django is subject to SQL injection through its column aliasesGHSA-6w2r-r2m5-xq5w

HIGHFix: django/django@102965e

GHSA-6w2r-r2m5-xq5w is a high-severity (CVSS 7.1) SQL Injection vulnerability in django. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for django — see the affected versions and patch details below.

Also known asBIT-django-2025-57833CVE-2025-57833PYSEC-2025-105
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
1 known
Exploitation data as of Nov 10, 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.
  • A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-6w2r-r2m5-xq5w.

EPSS Exploitation Probability

via FIRST.org ↗
28.3%probability of exploitation in next 30 days
Moderate Risk+12.62%
Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk
0.00%12.2%24.5%36.7%0.0%15.7%28.3%May 26Sep 26Nov 26

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

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 4.2 before 4.2.24, 5.1 before 5.1.12, and 5.2 before 5.2.6. FilteredRelation is subject to SQL injection in column aliases, using a suitably crafted dictionary, with dictionary expansion, as the **kwargs passed QuerySet.annotate() or QuerySet.alias().

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIdjangoall versions4.2.24pip install --upgrade 'django==4.2.24'
🐍PyPIdjango≥ 5.0a1&&< 5.1.125.1.12pip install --upgrade 'django==5.1.12'
🐍PyPIdjango≥ 5.2a1&&< 5.2.65.2.6pip install --upgrade 'django==5.2.6'

Affected Products

1 product · 3 configurations
Application
djangodjangoproject
≥ 5.2 && < 5.2.6
range
Exploits & PoCs
1

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 4.2.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6w2r-r2m5-xq5w is resolved across your whole dependency graph.

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

Red HatImportant
Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for GHSA-6w2r-r2m5-xq5w (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Ansible Automation Platform 2.4 for RHEL 8python3x-django-0:4.2.24-1.el8apRHSA-2025:16403
Red Hat Ansible Automation Platform 2.4 for RHEL 8ansible-automation-platform-24/lightspeed-rhel8:2.4.250225-18RHSA-2025:16404
Red Hat Ansible Automation Platform 2.5 for RHEL 8automation-controller-0:4.6.20-1.el8apRHSA-2025:16487
Red Hat Ansible Automation Platform 2.5 for RHEL 8ansible-automation-platform-25/lightspeed-rhel8:2.5.250924-1RHSA-2025:16514
Red Hat OpenStack Platform 16.2python-django20-0:2.0.13-20.el8ostRHSA-2025:17499
Red Hat OpenStack Platform 17.1 for RHEL 9python-django-0:2.2.24-12.el9ostRHSA-2025:17498
Red Hat OpenStack Services on OpenShift 18.0python-django-0:3.2.12-9.el9ostRHSA-2025:17500
Red Hat Satellite 6.15 for RHEL 8python-django-0:4.2.24-0.1.el8pcRHSA-2025:17614

Frequently Asked Questions

An issue was discovered in Django 4.2 before 4.2.24, 5.1 before 5.1.12, and 5.2 before 5.2.6. FilteredRelation is subject to SQL injection in column aliases, using a suitably crafted dictionary, with dictionary expansion, as the **kwargs passed QuerySet.annotate() or QuerySet.alias().
O3 Security · Impact-Aware SCA

Is GHSA-6w2r-r2m5-xq5w in your dependencies?

Find it across PyPI, including transitive dependencies.

Django is subject to SQL injection through its column…