CVE-2026-25674 Vulnerability Analysis & Exploit Details

CVE-2026-25674
Vulnerability Scoring

3.7
/10
Moderate Risk

Exploiting CVE-2026-25674 requires specific conditions, leading to a moderate security impact.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-25674 Details

Status: Analyzed

Last updated: 🕑 05 Mar 2026, 14:07 UTC
Originally published on: 🕒 03 Mar 2026, 15:16 UTC

Time between publication and last update: 1 days

CVSS Release: version 3

CVSS3 Source

134c704f-9b21-4f2e-91b3-4a467353bcc0

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2026-25674 Vulnerability Summary

CVE-2026-25674: 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.

Assessing the Risk of CVE-2026-25674

Access Complexity Graph

The exploitability of CVE-2026-25674 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-25674

CVE-2026-25674 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-25674, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-25674, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2026-25674 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: None
    CVE-2026-25674 poses no threat to data integrity.
  • Availability: None
    CVE-2026-25674 does not impact system availability.

CVE-2026-25674 References

External References

CWE Common Weakness Enumeration

CWE-362

CAPEC Common Attack Pattern Enumeration and Classification

  • Leveraging Race Conditions CAPEC-26 The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with their version and cause the system to read the malicious file.
  • Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions CAPEC-29 This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.

Vulnerable Configurations

  • cpe:2.3:a:djangoproject:django:4.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.7:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.7:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.8:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.8:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.9:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.9:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2:a1:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2:a1:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2:b1:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2:b1:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.10:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.10:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.11:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.11:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.12:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.12:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.13:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.13:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.14:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.14:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.15:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.15:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.16:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.16:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.17:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.17:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.18:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.18:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.19:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.19:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.20:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.20:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.21:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.21:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.22:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.22:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.23:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.23:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.24:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.24:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.25:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.25:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.26:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.26:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.28:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.28:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2.7:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2.7:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2.8:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2.8:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2.10:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2.10:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2.11:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2.11:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:6.0:-:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:6.0:-:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:6.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:6.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:6.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:6.0.2:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-25674: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-4867 – Impact: A bad regular expression is generated any time you have three or more parameters within a single segment, separated by something that is n...
  • CVE-2026-3116 – Mattermost Plugins versions <=11.4 11.0.4 11.1.3 11.3.2 10.11.11.0 fail to validate incoming request size which allows an authenticated attacker to...
  • CVE-2026-3115 – Mattermost versions 11.2.x <= 11.2.2, 10.11.x <= 10.11.10, 11.4.x <= 11.4.0, 11.3.x <= 11.3.1 fail to apply view restrictions when retrieving group...
  • CVE-2026-3114 – Mattermost versions 11.4.x <= 11.4.0, 11.3.x <= 11.3.1, 11.2.x <= 11.2.3, 10.11.x <= 10.11.11 fail to validate decompressed archive entry sizes dur...
  • CVE-2026-3113 – Mattermost versions 11.4.x <= 11.4.0, 11.3.x <= 11.3.1, 11.2.x <= 11.2.3, 10.11.x <= 10.11.11 fail to set permissions on downloaded bulk export whi...