CVE-2025-59682: PYSEC-2026-1296 - Django vulnerable to partial directory traversal via archives

Quick answers

Is CVE-2025-59682 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-59682 being exploited in the wild.

How severe is CVE-2025-59682?

Low severity, with a CVSS score of 3.1, published 7 July 2026.

Which products and versions are affected?

Django (PyPI) ECOSYSTEM:introduced=4.2,fixed=4.2.25, ECOSYSTEM:introduced=4.2,fixed=4.2.25,introduced=5.1,fixed=5.1.13,introduced=5.2,fixed=5.2.7.

Is there a fix for CVE-2025-59682?

Yes. Django (PyPI): upgrade to 4.2.25, 5.2.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2025-59682?

Check whether you run Django (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

• Django (PyPI): upgrade to 4.2.25, 5.2.7 or later

  pip install "Django>=5.2.7"

Affected products

• Django (PyPI) ECOSYSTEM:introduced=4.2,fixed=4.2.25, ECOSYSTEM:introduced=4.2,fixed=4.2.25,introduced=5.1,fixed=5.1.13,introduced=5.2,fixed=5.2.7

Identifiers

• CVE-2025-59682
• GHSA-q95w-c7qg-hrff
• PYSEC-2026-1296