How severe is CVE-2025-64459?

CVE-2025-64459 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2025-64459?

CVE-2025-64459 affects the following packages: django (PyPI), django (PyPI), django (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2025-64459?

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

How do I detect CVE-2025-64459 in my PyPI dependencies?

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.

How do I mitigate CVE-2025-64459 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2025-64459 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2025-64459, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2025-64459?

CVE-2025-64459 has an EPSS (Exploit Prediction Scoring System) score of 19.3%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2025-64459?

CVE-2025-64459 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-64459 published, and has it been updated?

CVE-2025-64459 was published on November 5, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

CRITICAL severity

CVE-2025-64459 — django

CRITICALFix: django/django@06dd383

CVE-2025-64459 is a critical-severity (CVSS 9.1) SQL Injection vulnerability in django. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for django — see the affected versions and patch details below.

Potential SQL injection via _connector keyword argument in QuerySet and Q objects

Also known asBIT-django-2025-64459GHSA-frmv-pr5f-9mcrPYSEC-2025-108

Published

Nov 5, 2025

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

1 known

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
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-64459.

EPSS Exploitation Probability

via FIRST.org ↗

19.3%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

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.1 before 5.1.14, 4.2 before 4.2.26, and 5.2 before 5.2.8. The methods QuerySet.filter(), QuerySet.exclude(), and QuerySet.get(), and the class Q(), are subject to SQL injection when using a suitably crafted dictionary, with dictionary expansion, as the _connector argument. 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 cyberstan for reporting this issue.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`django`	≥ 5.2a1&&< 5.2.8	5.2.8`pip install --upgrade 'django==5.2.8'`
🐍PyPI	`django`	≥ 5.0a1&&< 5.1.14	5.1.14`pip install --upgrade 'django==5.1.14'`
🐍PyPI	`django`	all versions	4.2.26`pip install --upgrade 'django==4.2.26'`

Affected Products

1 product · 3 configurations

Application

djangodjangoproject

≥ 5.2 && < 5.2.8

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52456webappsmultiple

Django 5.1.13 - SQL Injection

by Wafcontrol Security Team · Dec 3, 2025

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update django to 5.2.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-64459 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

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

The impact of this vulnerability on Red Hat products is limited to the effective user scope of the running process.

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-64459 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Ansible Automation Platform 2.5 for RHEL 8	`ansible-automation-platform-installer-0:2.5-20.el8ap`	RHSA-2025:23069
Red Hat Ansible Automation Platform 2.6 for RHEL 9	`automation-controller-0:4.7.6-1.el9ap`	RHSA-2025:23070
Red Hat Ansible Automation Platform 2.4	`ansible-automation-platform-24/lightspeed-rhel8:2.4`	RHSA-2025:23130
Red Hat Ansible Automation Platform 2.5	`ansible-automation-platform-25/lightspeed-rhel8:2.5`	RHSA-2025:23131
Red Hat Ansible Automation Platform 2.6	`ansible-automation-platform-26/controller-rhel9:4.7`	RHSA-2025:23133
Red Hat Ansible Automation Platform 2.6	`ansible-automation-platform-tech-preview/ansible-devspaces-rhel9:2.6-1765600296`	RHSA-2025:23196
Red Hat Ansible Automation Platform 2.6	`ansible-automation-platform-26/hub-rhel9:1768873505`	RHSA-2026:1596

Frequently Asked Questions

An issue was discovered in 5.1 before 5.1.14, 4.2 before 4.2.26, and 5.2 before 5.2.8. The methods `QuerySet.filter()`, `QuerySet.exclude()`, and `QuerySet.get()`, and the class `Q()`, are subject to SQL injection when using a suitably crafted dictionary, with dictionary expansion, as the `_connector` argument. 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 cyberstan for reporting this issue.

O3 Security · Impact-Aware SCA

Is CVE-2025-64459 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works