CVE-2025-59682 [Low] | Security Vulnerability in Django

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-11-21	0.09%	0.04%	-0.05%
2	2025-11-18	0.03%	0.09%	+0.06%
3	2025-10-23	—	0.03%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-11-21

0.09%

0.04%

-0.05%

2025-11-18

0.03%

0.09%

+0.06%

2025-10-23

—

0.03%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
3.1	3.1	LOW	`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	1.6	1.4	[email protected]
6.5	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	2.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

3.1

LOW

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

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

1.6

1.4

[email protected]

6.5

3.1

MEDIUM

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

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

2.8

3.6

[email protected]

OS Trackers for CVE-2025-59682

vendor	priority	summary	link
`alpine`	low	CVE-2025-59682: 1 source package rows (py3-django); 2 state rows across 2 repos (3.22-community, edge-community); fixed 2, open 0.	https://security.alpinelinux.org/vuln/CVE-2025-59682
`debian`	not yet assigned	CVE-2025-59682 not yet assigned priority: Debian including 1 source packages (python-django), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2025-59682
`redhat`	high	—	https://access.redhat.com/security/cve/CVE-2025-59682
`suse`	high	CVE-2025-59682 severity important: SUSE including 11 source package names (python3-Django-2.2.28-bp156.21.1, python311-Django-4.2.11-150600.3.33.1, …), 14 product×package rows across 6 product lines (SUSE Linux Enterprise Module for Package Hub 15 SP6, SUSE Linux Enterprise Module for Package Hub 15 SP7, … (6 product lines)): Fixed 14.	https://www.suse.com/security/cve/CVE-2025-59682/
`ubuntu`	medium	CVE-2025-59682 medium priority: Ubuntu including 1 source packages (python-django), 9 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): released 9.	https://ubuntu.com/security/CVE-2025-59682

Affected software / configurations for CVE-2025-59682

Vendor	Product	Version	Raw CPE
djangoproject	django	>= 4.2.0, < 4.2.25	cpe:2.3:a:djangoproject:django::::::::
djangoproject	django	>= 5.1, < 5.1.13	cpe:2.3:a:djangoproject:django::::::::
djangoproject	django	>= 5.2, < 5.2.7	cpe:2.3:a:djangoproject:django::::::::

References for CVE-2025-59682

URL	Tags
https://docs.djangoproject.com/en/dev/releases/security/	Vendor Advisory
https://groups.google.com/g/django-announce	Release Notes Vendor Advisory
https://www.djangoproject.com/weblog/2025/oct/01/security-releases/	Release Notes Vendor Advisory
http://www.openwall.com/lists/oss-security/2025/10/01/3

URL

CVE-2025-59682

Exploit prediction scoring system (EPSS) score for CVE-2025-59682

Common vulnerability scoring system (CVSS) metrics for CVE-2025-59682

Weakness enumeration for CVE-2025-59682

GitHub Security Advisory for CVE-2025-59682

OS Trackers for CVE-2025-59682

Affected software / configurations for CVE-2025-59682

References for CVE-2025-59682