diff options
| author | Natalia <124304+nessita@users.noreply.github.com> | 2025-05-07 10:59:55 -0300 |
|---|---|---|
| committer | Natalia <124304+nessita@users.noreply.github.com> | 2025-05-07 11:09:35 -0300 |
| commit | 05fab4e394e98bfd6c7a333d0d195438ccfa5450 (patch) | |
| tree | 758d24e8cb73b62d8892ab76826500209c48e6b1 | |
| parent | 2eb42068c216f136b0c970b9f01bad330e065a45 (diff) | |
[5.1.x] Added CVE-2025-32873 to security archive.
Backport of fdabda4e05587347aeb3382a442d7e77c1a0c3e5 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 1f7d2542ff..a4b2d21022 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. +May 7, 2025 - :cve:`2025-32873` +------------------------------- + +Denial-of-service possibility in `strip_tags()`. +`Full description +<https://www.djangoproject.com/weblog/2025/may/07/security-releases/>`__ + +* Django 5.2 :commit:`(patch) <c9731dc656e533187b021b4d81f8293d6c943a43>` +* Django 5.1 :commit:`(patch) <0b42f6a528df966729b24ecaaed67f85e5edc3dc>` +* Django 4.2 :commit:`(patch) <9cd8028f3e38dca8e51c1388f474eecbe7d6ca3c>` + April 2, 2025 - :cve:`2025-27556` --------------------------------- |