CVE-2026-1287 is a SQL injection vulnerability identified in the Django web framework affecting versions 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28. The vulnerability stems from improper neutralization of special elements used in SQL commands, specifically within the FilteredRelation feature. FilteredRelation allows complex query annotations by passing dictionaries expanded as keyword arguments (**kwargs) to QuerySet methods such as annotate(), aggregate(), extra(), values(), values_list(), and alias(). When these dictionaries contain control characters in column aliases, they can manipulate the underlying SQL query structure, enabling injection of arbitrary SQL code. This flaw is categorized under CWE-89 (Improper Neutralization of Special Elements used in an SQL Command). Exploitation requires the attacker to have low privileges (PR:L) but no user interaction (UI:N) and can be performed remotely (AV:N). The impact includes potential unauthorized disclosure and modification of data (confidentiality and integrity impacts), but no direct availability impact. Earlier unsupported Django versions (5.0.x, 4.1.x, 3.2.x) may also be vulnerable but were not formally evaluated. No public exploits have been reported yet. The vulnerability was responsibly disclosed by Solomon Kebede and is assigned a CVSS v3.1 base score of 5.4 (medium severity).

This vulnerability allows attackers with limited privileges to inject malicious SQL code through crafted dictionary expansions in Django QuerySet methods, potentially leading to unauthorized data access or modification. The confidentiality and integrity of backend databases can be compromised, exposing sensitive information or allowing data tampering. Since Django is widely used for web applications, especially in enterprise and public-facing services, exploitation could affect numerous organizations globally. Although no availability impact is noted, the breach of data confidentiality and integrity can result in regulatory penalties, reputational damage, and operational disruptions. Attackers could leverage this flaw to escalate privileges or pivot to other parts of the network if combined with other vulnerabilities. The ease of exploitation and the common usage of affected Django versions increase the risk profile for organizations that have not applied patches or mitigations.

1. Upgrade Django to the latest patched versions: 6.0.2 or later, 5.2.11 or later, and 4.2.28 or later. 2. Avoid using dynamic dictionary expansions (**kwargs) with untrusted input in QuerySet methods like annotate(), aggregate(), extra(), values(), values_list(), and alias(). 3. Implement strict input validation and sanitization on any user-supplied data that could influence query parameters or aliases. 4. Employ database-level security controls such as least privilege access for database users to limit damage from potential injection. 5. Use Django’s ORM features as intended and avoid raw SQL queries or unsafe query constructions. 6. Monitor application logs for unusual query patterns or errors that may indicate attempted exploitation. 7. Conduct security code reviews focusing on query construction and parameter handling. 8. Consider deploying Web Application Firewalls (WAFs) with rules to detect and block SQL injection attempts targeting Django applications. 9. Educate developers on secure coding practices related to ORM usage and SQL injection risks.