GHSA-q95w-c7qg-hrff BIT-django-2025-59682 CVE-2025-59682 PYSEC-2026-1296

Django vulnerable to partial directory traversal via archives

Medium PyPI

Severity: 3.1 / 10; Medium · CVSS 3.1
Exploit chance (EPSS): 0.93%; Chance of exploitation in the next 30 days. Higher than 60.71% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-23 Relative Path Traversal
Fix: 4.2.25; Upgrade django to this version or later

Description

An issue was discovered in Django 4.2 before 4.2.25, 5.1 before 5.1.13, and 5.2 before 5.2.7. The django.utils.archive.extract() function, used by the "startapp --template" and "startproject --template" commands, allows partial directory traversal via an archive with file paths sharing a common prefix with the target directory.

Affected versions

PyPI

Package	Vulnerable	Fixed in
django	`>= 4.2, < 4.2.25`	`4.2.25`
django	`>= 5.1, < 5.1.13`	`5.1.13`
django	`>= 5.2, < 5.2.7`	`5.2.7`
django	`>= 4.2, < 4.2.25` `>= 5.1, < 5.1.13` `>= 5.2, < 5.2.7`	`4.2.25` `5.1.13` `5.2.7`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

django PyPI → `4.2.25`

pip

pip install --upgrade "django>=4.2.25"

poetry

poetry add "django>=4.2.25"

uv

uv add "django>=4.2.25"

Severity breakdown

CVSS 3.1 3.1

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

Attack vector: Network
Attack complexity: High
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Weakness

CWE-23: Relative Path Traversal

The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory.

How to prevent it

Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright. When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434. Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would b
Implementation: Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked. Use a built-in path canonicalization function (such as realpath() in C) that produces the canonical version of the pathname, which effectively removes ".." sequences and symbolic links (CWE-23, CWE-59). This includes: realpath() in C getCanonicalPath() in Java GetFullPath() in ASP.NET realpath() or abs_path() in Perl realpath() in PHP
Operation: Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].

References

Advisories

Packages

Timeline

Oct 1, 2025 Published
Oct 12, 2026 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-q238-5cxm-5c9h Django GeoDjango vulnerable to denial of service through deeply nested geometry collections	Medium	Also affects django
GHSA-wvqv-fj8w-qmhm Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing	High	Also affects django
GHSA-8qcx-xf44-272x Django: DomainNameValidator permits newline characters that may enable HTTP header injection	Medium	Also affects django
GHSA-crhf-3pfg-w68w Django: GDALRaster may over-read heap memory when constructed from bytes	Medium	Also affects django
GHSA-3h9f-r86x-qvjx Django: cache middleware may expose private responses when unrelated request cookies are present	Medium	Also affects django
GHSA-8cjm-8mp7-r2xf Django: UpdateCacheMiddleware may disclose cached responses due to case-sensitive Cache-Control handling	Medium	Also affects django
GHSA-mm6v-q8q9-pgcf Django fails to prevent reuse of a partially-initialized connection after a failed `STARTTLS` handshake	Low	Also affects django
GHSA-h7pc-vwp9-298g Django: signed cookies are vulnerable to salt namespace collisions	Medium	Also affects django

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor