Is CVE-2025-64459 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-64459 being exploited in the wild.

How severe is CVE-2025-64459?

Critical severity, with a CVSS score of 9.1, published 5 November 2025.

Which products and versions are affected?

Django (PyPI) ECOSYSTEM:introduced=4.2,fixed=4.2.26,introduced=5.1,fixed=5.1.14,introduced=5.2,fixed=5.2.8, ECOSYSTEM:introduced=5.2a1,fixed=5.2.8.

Is there a fix for CVE-2025-64459?

Yes. Django (PyPI): upgrade to 5.2.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-64459 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2025-64459?

Check whether you run Django (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-64459: Django SQL injection in QuerySet and Q objects via _connector argument

CVE-2025-64459 · Severity: critical · CVSS 9.1 · Published 2025-11-05

Django, a popular web framework used to build websites, is vulnerable to a serious security flaw that could allow attackers to manipulate database queries. By sending specially crafted data to certain search or filtering functions, an attacker could potentially view, modify, or delete sensitive information stored in the application's database. This issue affects several versions of Django and requires immediate patching to protect user data and maintain system integrity.

Technologies: Django (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2025-64459 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-64459 being exploited in the wild.
How severe is CVE-2025-64459?: Critical severity, with a CVSS score of 9.1, published 5 November 2025.
Which products and versions are affected?: Django (PyPI) ECOSYSTEM:introduced=4.2,fixed=4.2.26,introduced=5.1,fixed=5.1.14,introduced=5.2,fixed=5.2.8, ECOSYSTEM:introduced=5.2a1,fixed=5.2.8.
Is there a fix for CVE-2025-64459?: Yes. Django (PyPI): upgrade to 5.2.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-64459 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-64459?: Check whether you run Django (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Django (PyPI): upgrade to 5.2.8 or later
```
pip install "Django>=5.2.8"
```

Technical details

A SQL injection vulnerability exists in Django's QuerySet methods (filter(), exclude(), get()) and the Q() class. The flaw is triggered when a crafted dictionary is passed as the _connector keyword argument using dictionary expansion. An attacker can exploit this to inject arbitrary SQL commands into the database query. The vulnerability stems from improper neutralization of special elements in the _connector argument. Patches are available in versions 5.2.8, 5.1.14, and 4.2.26.

Affected products

Django Software Foundation Django >= 5.2a1, < 5.2.8; >= 5.0a1, < 5.1.14; < 4.2.26

Identifiers

CVE-2025-64459
GHSA-frmv-pr5f-9mcr
PYSEC-2025-108

Timeline

2025-11-05: disclosed
2025-11-05: patched
2025-11-05: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.