How severe is CVE-2025-64460?

CVE-2025-64460 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2025-64460 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (80th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-64460?

CVE-2025-64460 affects Djangoproject Django. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-64460?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-64460 have an EU (EUVD) identifier?

Yes. CVE-2025-64460 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-200248.

When was CVE-2025-64460 published?

CVE-2025-64460 was published on 2025-12-02 and last updated on 2026-06-17.

CVE-2025-64460

CVE-2025-64460 is a high-severity vulnerability in Djangoproject Django with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-407.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 2% (80th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-200248
Weakness: CWE-407
Affected product: Djangoproject Django
Published: 2025-12-02
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2025-64460?: 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.
How severe is CVE-2025-64460?: CVE-2025-64460 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2025-64460 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (80th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-64460?: CVE-2025-64460 affects Djangoproject Django. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-64460?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-64460 have an EU (EUVD) identifier?: Yes. CVE-2025-64460 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-200248.
When was CVE-2025-64460 published?: CVE-2025-64460 was published on 2025-12-02 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*

More vulnerabilities in Djangoproject Django

CVE-2014-0474 — Critical (CVSS 10.0): The (1) FilePathField, (2) GenericIPAddressField, and (3) IPAddressField model field classes in Django before 1.4.11,…
CVE-2026-4277 — Critical (CVSS 9.8): An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Add permissions on inline model…
CVE-2024-53908 — Critical (CVSS 9.8): An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. Direct usage of the…
CVE-2023-31047 — Critical (CVSS 9.8): In Django 3.2 before 3.2.19, 4.x before 4.1.9, and 4.2 before 4.2.1, it was possible to bypass validation when using…
CVE-2022-34265 — Critical (CVSS 9.8): An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions…
CVE-2022-28347 — Critical (CVSS 9.8): A SQL injection issue was discovered in QuerySet.explain() in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0…

All CVEs affecting Djangoproject Django →

Other CWE-407 vulnerabilities

CVE-2026-58226 — High (CVSS 8.7): Inefficient Algorithmic Complexity vulnerability in elixir-mint hpax allows unauthenticated denial-of-service via…
CVE-2026-54892 — High (CVSS 8.7): Inefficient algorithmic complexity in Plug's nested-parameter decoder allows an unauthenticated remote attacker to…
CVE-2026-59094 — High (CVSS 7.5): Pathway through 0.31.1, fixed in commit d09722e, document store applies a caller-supplied glob pattern to indexed…
CVE-2026-53433 — High (CVSS 7.5): fzf is vulnerable to a Denial of Service (DoS) due to inefficient HTTP body processing in the --listen mode due to…
CVE-2026-13311 — High (CVSS 7.5): shell-quote prior to 1.8.5 finalizes parsed tokens in parse() using Array.prototype.concat as a reduce accumulator,…
CVE-2026-48516 — High (CVSS 7.5): MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301 and 3.1.7,…

Browse all CWE-407 vulnerabilities →