Advisory record · GHSA-6426-9fv3-65x8

Django has an SQL Injection issue

CVSS 5.4 MediumEPSS 0.0090 · 60th percentile

Published by the GitHub Advisory Database at 3 Feb 2026, 15:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
djangoPyPI>=6.0a1, <6.0.2 || >=5.2a1, <5.2.11 || >=4.2a1, <4.2.286.0.2, 5.2.11, 4.2.28
Identifiers
GHSA-6426-9fv3-65x8 · BIT-django-2026-1312 · CVE-2026-1312 · PYSEC-2026-47
Weakness (CWE)
CWE-89
Published
3 Feb 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Django versions 4.2 before 4.2.28, 5.2 before 5.2.11, and 6.0 before 6.0.2 are vulnerable to SQL injection through QuerySet.order_by() when column aliases containing periods are used with FilteredRelation and a crafted dictionary expanded into the query. The source does not describe the attacker's required access or privileges. Upgrade to Django 4.2.28, 5.2.11, or 6.0.2, depending on the series in use. Earlier unsupported series such as 5.0.x, 4.1.x, and 3.2.x were not evaluated and may also be affected.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.4 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0090, the 60th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:34 UTC First seen by agentprime
  2. 31 Oct 2026, 14:34 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.