| 1 |
=========================== |
| 2 |
Django 5.1.10 release notes |
| 3 |
=========================== |
| 4 |
|
| 5 |
*June 4, 2025* |
| 6 |
|
| 7 |
Django 5.1.10 fixes a security issue with severity "low" in 5.1.9. |
| 8 |
|
| 9 |
CVE-2025-48432: Potential log injection via unescaped request path |
| 10 |
================================================================== |
| 11 |
|
| 12 |
Internal HTTP response logging used ``request.path`` directly, allowing control |
| 13 |
characters (e.g. newlines or ANSI escape sequences) to be written unescaped |
| 14 |
into logs. This could enable log injection or forgery, letting attackers |
| 15 |
manipulate log appearance or structure, especially in logs processed by |
| 16 |
external systems or viewed in terminals. |
| 17 |
|
| 18 |
Although this does not directly impact Django's security model, it poses risks |
| 19 |
when logs are consumed or interpreted by other tools. To fix this, the internal |
| 20 |
``django.utils.log.log_response()`` function now escapes all positional |
| 21 |
formatting arguments using a safe encoding. |