Vulnerabilities · 2025 · Djangoproject
CVE-2025-48432
Djangoproject Django vulnerability
An issue was discovered in Django 5.2 before 5.2.3, 5.1 before 5.1.11, and 4.2 before 4.2.23. Internal HTTP response logging does not escape request.path, which allows remote attackers to potentially manipulate log output via crafted URLs. This may lead to log injection or forgery when logs are viewed in terminals or processed by external systems.
Affected products
Django, Debian Linux. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Djangoproject Django runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- docs.djangoproject.com/en/dev/releases/security/ · Vendor Advisory
- groups.google.com/g/django-announce · Vendor Advisory
- www.djangoproject.com/weblog/2025/jun/04/security-releases/ · Vendor Advisory
- www.openwall.com/lists/oss-security/2025/06/04/5 · Third Party Advisory
- www.openwall.com/lists/oss-security/2025/06/10/2 · Third Party Advisory
- www.openwall.com/lists/oss-security/2025/06/10/3 · Third Party Advisory
- www.djangoproject.com/weblog/2025/jun/10/bugfix-releases/
- www.openwall.com/lists/oss-security/2025/06/10/4
- nvd.nist.gov/vuln/detail/CVE-2025-48432
- cve.org/CVERecord?id=CVE-2025-48432
More vulnerabilities in Djangoproject products
CVE-2026-1312CVE-2026-1287CVE-2026-1285CVE-2026-1207CVE-2025-64460CVE-2025-64459CVE-2025-64458CVE-2025-59682All 137
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.