{"answers":{"affected":"8 open source packages ship an affected version, including django and Django. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-64460 in the wild and no public exploit code.","fix":"Upgrade django to a fixed version for your release line: 4.2.27, 5.1.15 or 5.2.9.","what":"CVE-2025-64460 is a high-severity denial of service vulnerability in Djangoproject Django, published on 2 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-64460 and fix it if it is affected.\n\nWhat it is: CVE-2025-64460 is a high-severity denial of service vulnerability in Djangoproject Django, published on 2 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-64460 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django (Bitnami): affected from 4.2.0; fixed in 4.2.27, 5.1.15, 5.2.9\n- django (PyPI): affected from 4.2; fixed in 4.2.27, 5.1.15, 5.2.9\n- django (PyPI): affected from 4.2a1; fixed in 4.2.27\n- django (PyPI): affected from 5.1a1; fixed in 5.1.15\n- django (PyPI): affected from 5.2a1; fixed in 5.2.9\n- Django (PyPI): affected from 4.2a1; fixed in 4.2.27\n- Django (PyPI): affected from 5.1a1; fixed in 5.1.15\n- Django (PyPI): affected from 5.2a1; fixed in 5.2.9\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-64460/ (Markdown: https://insights.sbomify.com/CVE-2025-64460/index.md)","id":"CVE-2025-64460","markdown":"https://insights.sbomify.com/CVE-2025-64460/index.md","name":"CVE-2025-64460","record":{"aliases":["BIT-django-2025-64460","CLSA-2026-1787225546","DEBIAN-CVE-2025-64460","ECHO-b160-53db-8b4b","GHSA-vrcr-9hj9-jcg6","MINI-r6r3-3x7c-jjww","OESA-2025-2788","OESA-2025-2789","OESA-2025-2790","OESA-2026-1342","PYSEC-2025-109","UBUNTU-CVE-2025-64460"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Django web framework","requires_auth":"none","summary":"Remote attackers can cause denial of service via CPU and memory exhaustion in Django's XML serializer through specially crafted input.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"DSF","cpe":[{"product":"django","vendor":"djangoproject"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-407","name":"Inefficient Algorithmic Complexity"}],"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.\nAlgorithmic 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`.\nEarlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.\nDjango would like to thank Seokchan Yoon for reporting this issue.","ecosystems":["Bitnami","PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Potential denial-of-service vulnerability in XML serializer text extraction","id":"CVE-2025-64460","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"djangoproject:django","products":["djangoproject:django"],"type":"denial_of_service","year":"2025"},"n_packages":8,"n_references":3,"next":{"headline":"Out of Bounds Write in mgocre_SH_25_3!RevBL() in NI LabVIEW","id":"CVE-2025-64461"},"packages":[{"ecosystem":"Bitnami","fixed":["4.2.27","5.1.15","5.2.9"],"introduced":["4.2.0","5.1.0","5.2.0"],"last_affected":[],"package":"django","purl":"pkg:bitnami/django","source":"BIT-django-2025-64460"},{"ecosystem":"PyPI","fixed":["4.2.27"],"introduced":["4.2a1"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-vrcr-9hj9-jcg6"},{"ecosystem":"PyPI","fixed":["5.1.15"],"introduced":["5.1a1"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-vrcr-9hj9-jcg6"},{"ecosystem":"PyPI","fixed":["5.2.9"],"introduced":["5.2a1"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-vrcr-9hj9-jcg6"},{"ecosystem":"PyPI","fixed":["4.2.27","5.1.15","5.2.9"],"introduced":["4.2","5.1","5.2"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"PYSEC-2025-109"},{"ecosystem":"PyPI","fixed":["4.2.27"],"introduced":["4.2a1"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-vrcr-9hj9-jcg6"},{"ecosystem":"PyPI","fixed":["5.1.15"],"introduced":["5.1a1"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-vrcr-9hj9-jcg6"},{"ecosystem":"PyPI","fixed":["5.2.9"],"introduced":["5.2a1"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-vrcr-9hj9-jcg6"}],"prev":{"headline":"Potential SQL injection via _connector keyword argument in QuerySet and Q objects","id":"CVE-2025-64459"},"products":["Django"],"published":"2025-12-02","related":[{"cvss_score":9.8,"headline":"Privilege abuse in GenericInlineModelAdmin","id":"CVE-2026-4277","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":9.8,"headline":"Django SQL injection in HasKey(lhs, rhs) on Oracle","id":"CVE-2024-53908","kev_date_added":null,"published":"2024-12-06"},{"cvss_score":9.8,"headline":"Django SQL injection vulnerability","id":"CVE-2024-42005","kev_date_added":null,"published":"2024-08-07"},{"cvss_score":9.8,"headline":"Django bypasses validation when using one form field to upload multiple files","id":"CVE-2023-31047","kev_date_added":null,"published":"2023-05-07"},{"cvss_score":9.8,"headline":"Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection","id":"CVE-2022-34265","kev_date_added":null,"published":"2022-07-04"},{"cvss_score":9.8,"headline":"SQL Injection in Django","id":"CVE-2021-35042","kev_date_added":null,"published":"2021-07-02"},{"cvss_score":9.8,"headline":"SQL injection in Django","id":"CVE-2020-7471","kev_date_added":null,"published":"2020-02-03"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-02","vendors":["djangoproject"]},"summary":"Remote attackers can cause denial of service via CPU and memory exhaustion in Django's XML serializer through specially crafted input.","url":"https://insights.sbomify.com/CVE-2025-64460/"}