diff options
| author | Sarah Boyce <42296566+sarahboyce@users.noreply.github.com> | 2025-03-06 14:04:36 +0100 |
|---|---|---|
| committer | Sarah Boyce <42296566+sarahboyce@users.noreply.github.com> | 2025-03-06 14:06:06 +0100 |
| commit | 2bfec6c84b6401dc6f18ccd1d9628e8a1e1ba2c6 (patch) | |
| tree | 99405708027286776bd5f989ec3649e16d999b72 | |
| parent | 0e2349207c80bfc6145ea0164a79837caa395277 (diff) | |
[5.2.x] Added CVE-2025-26699 to security archive.
Backport of bad1a18ff28a671f2fdfd447bdf8f43602f882c2 from main.
| -rw-r--r-- | docs/releases/security.txt | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/docs/releases/security.txt b/docs/releases/security.txt index 0a87b8b810..d55c7bf497 100644 --- a/docs/releases/security.txt +++ b/docs/releases/security.txt @@ -36,6 +36,17 @@ Issues under Django's security process All security issues have been handled under versions of Django's security process. These are listed below. +March 6, 2025 - :cve:`2025-26699` +--------------------------------- + +Potential denial-of-service in ``django.utils.text.wrap()``. +`Full description +<https://www.djangoproject.com/weblog/2025/mar/06/security-releases/>`__ + +* Django 5.1 :commit:`(patch) <8dbb44d34271637099258391dfc79df33951b841>` +* Django 5.0 :commit:`(patch) <4f2765232336b8ad0afd8017d9d912ae93470017>` +* Django 4.2 :commit:`(patch) <e88f7376fe68dbf4ebaf11fad1513ce700b45860>` + January 14, 2025 - :cve:`2024-56374` ------------------------------------ |