How severe is CVE-2026-1287?

CVE-2026-1287 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2026-1287?

CVE-2026-1287 affects the following packages: django (PyPI), django (PyPI), django (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-1287?

Update django to 6.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-1287 is resolved across your whole dependency graph.

How do I detect CVE-2026-1287 in my PyPI dependencies?

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.

How do I mitigate CVE-2026-1287 if there is no patch (or I can't update yet)?

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.

Is CVE-2026-1287 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-1287 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-1287?

CVE-2026-1287 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 58th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-1287?

CVE-2026-1287 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-1287 published, and has it been updated?

CVE-2026-1287 was published on February 3, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

CVE-2026-1287 — django

MEDIUMFix: django/django@e891a84

CVE-2026-1287 is a medium-severity (CVSS 5.4) SQL Injection vulnerability in django. A fix is available for django — see the affected versions and patch details below.

Potential SQL injection in column aliases via control characters

Also known asBIT-django-2026-1287GHSA-gvg8-93h5-g6qqPYSEC-2026-46

Published

Feb 3, 2026

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

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 CVE-2026-1287.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs58th percentile — riskier than 58% of all scored CVEsHighest risk

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 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28. FilteredRelation is subject to SQL injection in column aliases via control characters, using a suitably crafted dictionary, with dictionary expansion, as the **kwargs passed to QuerySet methods annotate(), aggregate(), extra(), values(), values_list(), and alias(). Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Solomon Kebede for reporting this issue.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`django`	≥ 6.0a1&&< 6.0.2	6.0.2`pip install --upgrade 'django==6.0.2'`
🐍PyPI	`django`	≥ 5.2a1&&< 5.2.11	5.2.11`pip install --upgrade 'django==5.2.11'`
🐍PyPI	`django`	≥ 4.2a1&&< 4.2.28	4.2.28`pip install --upgrade 'django==4.2.28'`

Affected Products

1 product · 3 configurations

Application

djangodjangoproject

≥ 6.0 && < 6.0.2

range

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update django to 6.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-1287 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.

Red HatImportant

This IMPORTANT SQL injection flaw in Django allows a remote attacker to execute arbitrary SQL commands by crafting column aliases. This vulnerability affects Red Hat products that incorporate Django, such as Red Hat Ansible Automation Platform, Red Hat Discovery, Red Hat Satellite, Insights, and Ansible Services,…

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 CVE-2026-1287 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Ansible Automation Platform 2.5 for RHEL 8	`python3.12-django-0:4.2.28-1.el8ap`	RHSA-2026:3959
Red Hat Ansible Automation Platform 2.6 for RHEL 9	`python3.12-django-0:4.2.28-1.el9ap`	RHSA-2026:3958
Red Hat Satellite 6.16 for RHEL 8	`python-django-0:4.2.28-0.1.el8pc`	RHSA-2026:5971
Red Hat Satellite 6.17 for RHEL 9	`foreman-0:3.14.0.14-1.el9sat`	RHSA-2026:5970
Red Hat Satellite 6.18 for RHEL 9	`python3.12-django-0:4.2.30-1.el9pc`	RHSA-2026:14835
Red Hat Ansible Automation Platform 2.5	`ansible-automation-platform-25/lightspeed-rhel8:1772214630`	RHSA-2026:3962
Red Hat Ansible Automation Platform 2.6	`ansible-automation-platform-26/lightspeed-rhel9:1772552788`	RHSA-2026:3960
Red Hat Discovery 2	`discovery/discovery-server-rhel9:1770913597`	RHSA-2026:2694

UbuntuMEDIUM

USN-8009-1Ubuntu

Frequently Asked Questions

An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28. `FilteredRelation` is subject to SQL injection in column aliases via control characters, using a suitably crafted dictionary, with dictionary expansion, as the `**kwargs` passed to `QuerySet` methods `annotate()`, `aggregate()`, `extra()`, `values()`, `values_list()`, and `alias()`. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Solomon Kebede for reporting this issue.

O3 Security · Impact-Aware SCA

Is CVE-2026-1287 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works