June 4, 2025

Django security releases issued: 5.2.2, 5.1.10, and 4.2.22

published by	Natalia Bidart
in blog	The Django weblog
original entry	Django security releases issued: 5.2.2, 5.1.10, and 4.2.22

In accordance with our security release policy, the Django team is issuing releases for Django 5.2.2, Django 5.1.10, and Django 4.2.22. These releases address the security issues detailed below. We encourage all users of Django to upgrade as soon as possible.

CVE-2025-48432: Potential log injection via unescaped request path

Internal HTTP response logging used request.path directly, allowing control characters (e.g. newlines or ANSI escape sequences) to be written unescaped into logs. This could enable log injection or forgery, letting attackers manipulate log appearance or structure, especially in logs processed by external systems or viewed in terminals.

Although this does not directly impact Django's security model, it poses risks when logs are consumed or interpreted by other tools. To fix this, the internal django.utils.log.log_response() function now escapes all positional formatting arguments using a safe encoding.

Thanks to Seokchan Yoon (https://ch4n3.kr/) for the report.

This issue has severity "moderate" according to the Django security policy.

Affected supported versions

Django main
Django 5.2
Django 5.1
Django 4.2

Resolution

Patches to resolve the issue have been applied to Django's main, 5.2, 5.1, and 4.2 branches. The patches may be obtained from the following changesets.

CVE-2025-48432: Potential log injection via unescaped request path

On the main branch
On the 5.2 branch
On the 5.1 branch
On the 4.2 branch

The following releases have been issued

Django 5.2.2 (download Django 5.2.2 | 5.2.2 checksums)
Django 5.1.10 (download Django 5.1.10 | 5.1.10 checksums)
Django 4.2.22 (download Django 4.2.22 | 4.2.22 checksums)

The PGP key ID used for this release is Natalia Bidart: 2EE82A8D9470983E

General notes regarding security reporting

As always, we ask that potential security issues be reported via private email to security@djangoproject.com, and not via Django's Trac instance, nor via the Django Forum. Please see our security policies for further information.