CVE-2025-64459: Django Package Vulnerability Leading to Potential Security Risks

django Updated 22 Oct 2026

Summary

25/11/2025
Yes i
Critical
9.1

CVE-2025-64459: ... Affects django versions < 5.2.1+echo.1. Fixed in 5.2.1+echo.1. How to fix ↓

Also tracked for

The same CVE-2025-64459 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Django is a high-level Python web framework that encourages rapid development and clean, pragmatic design. It is widely used for building web applications and provides a robust set of features, including an ORM, authentication, and an admin interface. However, like any software, it can be vulnerable to security issues, which can compromise the integrity and security of applications built using it.

Vulnerability Detail

CVE-2025-64459 is a vulnerability in the Django package that arises from improper handling of certain inputs, which could allow an attacker to execute unauthorized actions or access sensitive information. This vulnerability can lead to severe consequences, including data breaches and unauthorized access to user accounts. It is crucial for developers using Django to be aware of this vulnerability and take appropriate measures to mitigate the risks.

How To Fix

Latest published version: 6.1.2 as of 22 Oct 2026

pip install --upgrade "django==6.1.2"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

5.2.1+echo.1

This is the first release that contains the fix.

pip install --upgrade "django==5.2.1+echo.1"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If you are unable to immediately update Django, consider implementing input validation and sanitization to mitigate the risk of exploitation until you can apply the patch.

Conclusion

CVE-2025-64459 represents a significant security risk for applications using the Django framework. It is essential for developers to update their Django installations to the patched version to safeguard their applications from potential attacks. Regular monitoring and vulnerability management practices, such as using tools like Vulert, can help maintain application security.

See every vulnerability recorded for django →

Share this vulnerability

FAQ

CVE-2025-64459 is a security vulnerability in the Django package that can lead to unauthorized actions or data breaches.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Implement input validation and sanitization as a temporary measure to reduce the risk of exploitation.

Exploitation of this vulnerability could lead to unauthorized access to sensitive data, data breaches, and compromised user accounts.

Related vulnerabilities

Recent vulnerabilities recorded for django.

How To Fix

Latest published version: 6.1.2 as of 22 Oct 2026

pip install --upgrade "django==6.1.2"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

5.2.1+echo.1

This is the first release that contains the fix.

pip install --upgrade "django==5.2.1+echo.1"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback