CVE-2025-64460
No exploitation reported by the sources we read.
- Published2025-12-02
- Fixed in5.2.9 · 5.1.15 · 4.2.27
- WeaknessCWE-407
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
An issue was discovered in 5.2 before 5.2.9, 5.1 before 5.1.15, and 4.2 before 4.2.27. Algorithmic complexity in `django.core.serializers.xml_serializer.getInnerText()` allows a remote attacker to cause a potential denial-of-service attack triggering CPU and memory exhaustion via specially crafted XML input processed by the XML `Deserializer`. 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 Seokchan Yoon for reporting this issue.
Timeline
dates in UTC- 2025-12-0216:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2025-64460?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2025-64460?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 5.2 | ≥ 5.2, < 5.2.9 | 5.2.9 | NVD · OSV |
| 5.2 | ≥ 5.2.0, < 5.2.9 | 5.2.9 | OSV |
| 5.2 | ≥ 5.2a1, < 5.2.9 | 5.2.9 | OSV |
| 5.1 | ≥ 5.1, < 5.1.15 | 5.1.15 | NVD · OSV |
| 5.1 | ≥ 5.1.0, < 5.1.15 | 5.1.15 | OSV |
| 5.1 | ≥ 5.1a1, < 5.1.15 | 5.1.15 | OSV |
| 4.2 | ≥ 4.2, < 4.2.27 | 4.2.27 | NVD · OSV |
| 4.2 | ≥ 4.2.0, < 4.2.27 | 4.2.27 | OSV |
| 4.2 | ≥ 4.2a1, < 4.2.27 | 4.2.27 | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Django to 5.2.9 · 5.1.15 · 4.2.27
Advisories and patches
- docs.djangoproject.comPatch · Vendor Advisory
- groups.google.comRelease Notes
- www.djangoproject.comPatch · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2025-12-02
- Last Modified
- 2026-10-18
- NVD status
- Analyzed
Frequently asked questions
What is CVE-2025-64460?
Is CVE-2025-64460 actively exploited?
What is the CVSS score for CVE-2025-64460?
Running Django? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.