NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

CVE-2025-64460 — django

HIGHFix: django/django@0db9ea4

CVE-2025-64460 is a high-severity (CVSS 7.5) CWE-407 vulnerability in django. A fix is available for django — see the affected versions and patch details below.

Potential denial-of-service vulnerability in XML serializer text extraction

Also known asBIT-django-2025-64460GHSA-vrcr-9hj9-jcg6PYSEC-2025-109
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-64460.

EPSS Exploitation Probability

via FIRST.org ↗
2.2%probability of exploitation in next 30 days
Lower Risk+0.08%
Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk
0.00%0.93%1.86%2.79%0.1%2.2%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
🐍django🐍django🐍django

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIdjango≥ 5.2a1&&< 5.2.95.2.9pip install --upgrade 'django==5.2.9'
🐍PyPIdjango≥ 5.1a1&&< 5.1.155.1.15pip install --upgrade 'django==5.1.15'
🐍PyPIdjango≥ 4.2a1&&< 4.2.274.2.27pip install --upgrade 'django==4.2.27'

Affected Products

1 product · 3 configurations
Application
djangodjangoproject
≥ 5.2 && < 5.2.9
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update django to 5.2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-64460 is resolved across your whole dependency graph.

  3. Workarounds

    Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability is rated Important for Red Hat products that process XML input using Django's XML Deserializer, including Red Hat Ansible Automation Platform, Red Hat OpenStack Platform, and OpenShift Service Mesh. A remote attacker can exploit this flaw by providing specially crafted XML, leading to a…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Source: Red Hat security advisory for CVE-2025-64460 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Ansible Automation Platform 2.4 for RHEL 8automation-controller-0:4.5.30-1.el8apRHSA-2026:1497
Red Hat Ansible Automation Platform 2.5 for RHEL 8automation-controller-0:4.6.25-1.el8apRHSA-2026:1506
Red Hat Ansible Automation Platform 2.6 for RHEL 9automation-controller-0:4.7.8-1.el9apRHSA-2026:1249
Red Hat Ansible Automation Platform 2.4ansible-automation-platform-24/lightspeed-rhel8:1768268588RHSA-2026:1599
Red Hat Ansible Automation Platform 2.5ansible-automation-platform-25/lightspeed-rhel8:1768874696RHSA-2026:1609
Red Hat Discovery 2discovery/discovery-server-rhel9:1767888970RHSA-2026:0414
UbuntuHIGH
USN-7903-1Ubuntu

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2025-64460 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2025-64460: django — Fixed in 5.2.9