← Back
CVE-2025-64460
Vulnerability in django (CVE-2025-64460)
Summary
vulnerability in django (CVE-2025-64460). Risk of unauthorized operations or information disclosure. Exploitable via ``Deserializer``. Mitigation: upgrade to `4.2.27, 5.1.15, 5.2.9` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-64460** has been found in django.
Attackers can target a specific entry point like ``Deserializer`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade django to **4.2.27, 5.1.15, 5.2.9** or later.
If unsure, ask your IT team or search "django CVE-2025-64460" on the vendor's site.
CVE-2025-64460 (django) — CWE-407 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `Deserializer`
Patched: `4.2.27, 5.1.15, 5.2.9` — 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-407) exists in django. Attackers reach the vulnerable code path via ``Deserializer`` without authentication.
📍 Affected scope
django — . Attack surface: `Deserializer`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.2.27, 5.1.15, 5.2.9**.
🛡️ 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.27, 5.1.15, 5.2.9ステージング環境で 4.2.27, 5.1.15, 5.2.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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.27"},{"introduced":"5.1.0"},{"fixed":"5.1.15"},{"introduced":"5.2.0"},{"fixed":"5.2.9"}]}]
PyPI
django
[{"type":"ECOSYSTEM","events":[{"introduced":"4.2"},{"fixed":"4.2.27"},{"introduced":"5.1"},{"fixed":"5.1.15"},{"introduced":"5.2"},{"fixed":"5.2.9"}]}]
pip
Django
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.2.27"}]}]
References
- advisory https://groups.google.com/g/django-announce
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-64460
- advisory https://github.com/advisories/GHSA-vrcr-9hj9-jcg6
- package https://github.com/django/django
- patch https://docs.djangoproject.com/en/dev/releases/security/
- patch https://www.djangoproject.com/weblog/2025/dec/02/security-releases/
- web https://github.com/django/django/commit/0db9ea4669312f1f4973e09f4bca06ab9c1ec74b
- web https://github.com/django/django/commit/1dbd07a608e495a0c229edaaf84d58d8976313b5
- web https://github.com/django/django/commit/4d2b8803bebcdefd2b76e9e8fc528d5fddea93f0
- web https://github.com/django/django/commit/99e7d22f55497278d0bcb2e15e72ef532e62a31d
- web https://docs.djangoproject.com/en/dev/releases/security
- web https://www.djangoproject.com/weblog/2025/dec/02/security-releases
- web https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2025-109.yaml