← Back
CVE-2026-1287
medium
CVSS 5.4
SQL Injection in django (CVE-2026-1287)
Summary
SQL injection in django (CVE-2026-1287). Risk of unauthorized operations or information disclosure. Exploitable via ``FilteredRelation``. Mitigation: upgrade to `4.2.28, 5.2.11, 6.0.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-1287** has been found in django.
Attackers can target a specific entry point like ``FilteredRelation`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade django to **4.2.28, 5.2.11, 6.0.2** or later.
If unsure, ask your IT team or search "django CVE-2026-1287" on the vendor's site.
CVE-2026-1287 (django) — CWE-89 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `FilteredRelation` / `QuerySet`
Patched: `4.2.28, 5.2.11, 6.0.2` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**SQL injection** (CWE-89) exists in django. Attackers reach the vulnerable code path via ``FilteredRelation`` without authentication.
📍 Affected scope
django — . Attack surface: `FilteredRelation` / `QuerySet`.
🔥 Severity
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.2.28, 5.2.11, 6.0.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'django' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'django' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `django` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade django to 4.2.28, 5.2.11, 6.0.2ステージング環境で 4.2.28, 5.2.11, 6.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Bitnami
django
[{"type":"SEMVER","events":[{"introduced":"4.2.0"},{"fixed":"4.2.28"},{"introduced":"5.2.0"},{"fixed":"5.2.11"},{"introduced":"6.0.0"},{"fixed":"6.0.2"}]}]
PyPI
django
[{"type":"ECOSYSTEM","events":[{"introduced":"4.2"},{"fixed":"4.2.28"},{"introduced":"5.2"},{"fixed":"5.2.11"},{"introduced":"6.0"},{"fixed":"6.0.2"}]}]
pip
Django
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.2.28"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-1287
- advisory https://github.com/advisories/GHSA-gvg8-93h5-g6qq
- package https://github.com/django/django
- patch 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
- patch 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
- web 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
- web https://github.com/django/django/commit/e891a84c7ef9962bfcc3b4685690219542f86a22
- web https://docs.djangoproject.com/en/dev/releases/security
- web https://www.djangoproject.com/weblog/2026/feb/03/security-releases
- web https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2026-46.yaml
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c