CVE-2026-1207 is a medium-severity (CVSS 5.4) SQL Injection vulnerability in django. 1 public exploit reference exists, so weaponization risk is real. A fix is available for django — see the affected versions and patch details below.
Potential SQL injection via raster lookups on PostGIS
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-1207.
EPSS Exploitation Probability
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
CVE-2026-1207 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 378,156 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
django🐍django🐍djangoReal-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.
Raster lookups on RasterField (only implemented on PostGIS) allows remote attackers to inject SQL via the band index parameter.
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 Tarek Nakkouch for reporting this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | django | ≥ 6.0a1&&< 6.0.2 | 6.0.2pip install --upgrade 'django==6.0.2' |
| 🐍PyPI | django | ≥ 5.2a1&&< 5.2.11 | 5.2.11pip install --upgrade 'django==5.2.11' |
| 🐍PyPI | django | ≥ 4.2a1&&< 4.2.28 | 4.2.28pip install --upgrade 'django==4.2.28' |
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 dependencyDetect
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-1207 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-1207 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-1207. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect CVE-2026-1207
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2026-1207 -u https://target- Template
- Django RasterField - SQL Injection
- Severity
- high
- Impact
- Remote attackers can execute arbitrary SQL commands, potentially leading to data disclosure or modification.
- Remediation
- Upgrade to versions 6.0.2, 5.2.11, 4.2.28 or later.
Template by ProjectDiscovery nuclei-templates (omarkurt), MIT licensed. View the full template. Scan only systems you are authorised to test.
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.
This IMPORTANT flaw affects Django's `RasterField` when utilized with PostGIS, allowing remote SQL injection via the band index parameter. Red Hat Ansible Automation Platform, Red Hat Discovery, Red Hat Satellite, Insights, and Ansible Services are impacted if configured to use Django with PostGIS `RasterField`…
| 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 |
Frequently Asked Questions
Is CVE-2026-1207 in your dependencies?
O3 Security finds CVE-2026-1207 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.