VulnerabilityPublished 3 Mar 2026

CVE-2026-25674: djangoproject Django · Race Condition

Affects djangoproject DjangoSource CVE Database V5

Compare

Not known to be exploited · CVSS 3.7 Low · fixed in 6.0.3 : update djangoproject Django when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

3.7Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.0.3, 5.2.12, 4.2.29

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Django and django to 6.0.3, 5.2.12 or 4.2.29.

Affected software

Product	Affected	Fixed in
djangoprojectDjango	Affected >=6.0 <6.0.3	Fixed in 6.0.3
djangoprojectDjango	Affected >=5.2 <5.2.12	Fixed in 5.2.12
djangoprojectDjango	Affected >=4.2 <4.2.29	Fixed in 4.2.29
PyPIdjango`pkg:pypi/django`Other threats	Affected =6.0 =5.2 =4.2	Fixed in–
PyPIdjango`pkg:pypi/django`Other threats	Affected >=6.0 <6.0.3 >=5.2 <5.2.12 >=4.2 <4.2.29	Fixed in 6.0.3 5.2.12 4.2.29

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade affected Django versions to the patched releases: 6.0.3 or later, 5.2.12 or later, and 4.2.29 or later. If upgrading is not immediately feasible, mitigate risk by avoiding multi-threaded deployment configurations that handle concurrent requests affecting file creation or caching, or by switching to alternative storage and caching backends that do not rely on file-system permissions. Implement strict file permission auditing and monitoring to detect anomalous permission changes. Additionally, consider isolating Django application processes to minimize the impact of improper umask changes across threads. Review application code and deployment environments for any custom file permission handling that could exacerbate the issue. Employ runtime security tools to detect race conditions or unexpected file permission changes. Finally, maintain robust access controls and logging to quickly identify and respond to any exploitation attempts.

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.

Impact

The primary impact of this vulnerability is the potential for unauthorized access or modification of files due to incorrect file permissions set by concurrent requests exploiting the race condition. This can lead to confidentiality breaches if sensitive files become accessible to unauthorized users, integrity issues if files are modified maliciously, and potentially availability concerns if critical files are corrupted or deleted. Organizations running Django applications that rely on file-system storage or file-based caching in multi-threaded environments are at risk. Attackers with the ability to send concurrent requests to the application could exploit this flaw to escalate privileges or access sensitive data. The scope includes any Django deployment using affected versions and configurations, which is significant given Django's widespread use in web applications globally. The lack of known exploits in the wild suggests the vulnerability is not yet actively exploited, but the risk remains high due to the ease of triggering concurrent requests in web environments.

CWE-362Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition) (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product contains a concurrent code sequence that 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 operating concurrently.
Architecture and Design
In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
Architecture and Design
Use thread-safe capabilities such as the data access abstraction in Spring.
Architecture and Design
Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.11.2 (opens in a new tab)
Attack patterns
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (opens in a new tab)
Leveraging Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Mar 2026, 15:03 UTC

WeaknessesCWE-362

Technical details

References

Community reviews

Related threats