← Back
CVE-2026-3902
Vulnerability in django (CVE-2026-3902)
Summary
vulnerability in django (CVE-2026-3902). Data can be tampered with by attackers. Exploitable via ``ASGIRequest``. Mitigation: upgrade to `4.2.30, 5.2.13, 6.0.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-3902** has been found in django.
Attackers can target a specific entry point like ``ASGIRequest`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: ?/10.
What to do: upgrade django to **4.2.30, 5.2.13, 6.0.4** or later.
If unsure, ask your IT team or search "django CVE-2026-3902" on the vendor's site.
CVE-2026-3902 (django) — CWE-290 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `ASGIRequest`
Patched: `4.2.30, 5.2.13, 6.0.4` — 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
**A vulnerability** (CWE-290) exists in django. Attackers reach the vulnerable code path via ``ASGIRequest`` without authentication.
📍 Affected scope
django — . Attack surface: `ASGIRequest`.
🔥 Severity
Severity: ?. Data can be tampered with by attackers
🔧 How to fix
Update to **4.2.30, 5.2.13, 6.0.4**.
🛡️ 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.30, 5.2.13, 6.0.4ステージング環境で 4.2.30, 5.2.13, 6.0.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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.30"},{"introduced":"5.2.0"},{"fixed":"5.2.13"},{"introduced":"6.0.0"},{"fixed":"6.0.4"}]}]
PyPI
django
[{"type":"ECOSYSTEM","events":[{"introduced":"4.2"},{"fixed":"4.2.30"},{"introduced":"5.2"},{"fixed":"5.2.13"},{"introduced":"6.0"},{"fixed":"6.0.4"}]}]
pip
Django
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.2.30"}]}]
References
- advisory https://groups.google.com/g/django-announce
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-3902
- advisory https://github.com/advisories/GHSA-mvfq-ggxm-9mc5
- package https://github.com/django/django
- patch https://docs.djangoproject.com/en/dev/releases/security/
- patch https://www.djangoproject.com/weblog/2026/apr/07/security-releases/
- web https://docs.djangoproject.com/en/dev/releases/security
- web https://www.djangoproject.com/weblog/2026/apr/07/security-releases
- web https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2026-51.yaml