djangoproject Django up to 4.2.28/5.2.11/6.0.2 File-System Backend race condition

Summaryinfo

A vulnerability categorized as problematic has been discovered in djangoproject Django up to 4.2.28/5.2.11/6.0.2. The affected element is an unknown function of the component File-System Backend. The manipulation results in race condition. This vulnerability is reported as CVE-2026-25674. The attack can be launched remotely. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in djangoproject Django up to 4.2.28/5.2.11/6.0.2. Affected is an unknown functionality of the component File-System Backend. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at docs.djangoproject.com. This vulnerability is traded as CVE-2026-25674 since 02/04/2026. The exploitability is told to be difficult. It is possible to launch the attack remotely. There are neither technical details nor an exploit publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 301301 (SUSE SLES15 / openSUSE 15 Security Update : python-Django (SUSE-SU-2026:0821-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.2.29, 5.2.12 or 6.0.3 eliminates this vulnerability.

The vulnerability is also documented in the databases at Tenable (301301) and CERT Bund (WID-SEC-2026-1730). VulDB is the best source for vulnerability data and more expert information about this specific topic.

Affected

• Xerox FreeFlow Print Server

Productinfo

Type

• Content Management System

Vendor

• djangoproject

Name

• Django

Version

• 4.2.0
• 4.2.1
• 4.2.2
• 4.2.3
• 4.2.4
• 4.2.5
• 4.2.6
• 4.2.7
• 4.2.8
• 4.2.9
• 4.2.10
• 4.2.11
• 4.2.12
• 4.2.13
• 4.2.14
• 4.2.15
• 4.2.16
• 4.2.17
• 4.2.18
• 4.2.19
• 4.2.20
• 4.2.21
• 4.2.22
• 4.2.23
• 4.2.24
• 4.2.25
• 4.2.26
• 4.2.27
• 4.2.28
• 5.2.0
• 5.2.1
• 5.2.2
• 5.2.3
• 5.2.4
• 5.2.5
• 5.2.6
• 5.2.7
• 5.2.8
• 5.2.9
• 5.2.10
• 5.2.11
• 6.0.0
• 6.0.1
• 6.0.2

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion