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

django Updated 22 Oct 2026

Summary

25/11/2025
Yes i
High
7.5

CVE-2025-64458: ... 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-64458 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

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 comes with a plethora of features, including an ORM, authentication, and an admin interface. However, like any software, it can be susceptible to vulnerabilities that may compromise the security of applications built using it.

Vulnerability Detail

CVE-2025-64458 is a vulnerability in the Django package that allows attackers to exploit certain weaknesses in the framework. This vulnerability can lead to unauthorized access or manipulation of data, potentially compromising the integrity and confidentiality of applications. It originates from flaws in the way Django handles specific requests, making it crucial for developers to address this issue promptly to safeguard their applications.

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 update Django immediately, consider implementing strict input validation and sanitization to mitigate potential exploitation of this vulnerability. Additionally, review your application's access controls to limit exposure to sensitive data.

Conclusion

CVE-2025-64458 represents a significant security risk for applications using the Django framework. It is essential for developers to update to the patched version to protect their applications from potential exploitation. By staying informed and proactive, developers can ensure the security and integrity of their web applications.

See every vulnerability recorded for django →

Share this vulnerability

FAQ

CVE-2025-64458 is a security vulnerability in the Django web framework that could allow unauthorized access or manipulation of data.

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

If an immediate update is not possible, implement strict input validation and review your application's access controls to reduce risk.

Failing to address CVE-2025-64458 may lead to unauthorized access, data breaches, and potential loss of sensitive information.

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