Home

Description

An issue was discovered in 6.0 before 6.0.3, 5.2 before 5.2.12, and 4.2 before 4.2.29. Race condition in file-system storage and file-based cache backends in Django allows an attacker to cause file system objects to be created with incorrect permissions via concurrent requests, where one thread's temporary `umask` change affects other threads in multi-threaded environments. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Tarek Nakkouch for reporting this issue.

PUBLISHED Reserved 2026-02-04 | Published 2026-03-03 | Updated 2026-03-03 | Assigner DSF

Problem types

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Product status

Default status
unaffected

6.0 (semver) before 6.0.3
affected

6.0.3 (semver)
unaffected

5.2 (semver) before 5.2.12
affected

5.2.12 (semver)
unaffected

4.2 (semver) before 4.2.29
affected

4.2.29 (semver)
unaffected

Timeline

2026-01-20:Initial report received.
2026-02-20:Vulnerability confirmed.
2026-03-03:Security release issued.

Credits

Tarek Nakkouch reporter

Natalia Bidart remediation developer

Natalia Bidart coordinator

References

docs.djangoproject.com/en/dev/releases/security/ (Django security archive) vendor-advisory

groups.google.com/g/django-announce (Django releases announcements) mailing-list

www.djangoproject.com/weblog/2026/mar/03/security-releases/ (Django security releases issued: 6.0.3, 5.2.12, and 4.2.29) vendor-advisory

cve.org (CVE-2026-25674)

nvd.nist.gov (CVE-2026-25674)

Download JSON