Skip to main content
CVE-2025-59681VulnerabilityPublished Updated

SUSE · Security update for python-Django

Affects SUSESource GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2025-59681· High 7.1

Not known to be exploited · CVSS 7.1 High.

Data as of 16 Nov 2026, 00:49 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 15 Nov 2026.

What to do

AI-suggested

Apply the SUSE security update for python-Django that includes fixes for CVE-2025-59681 and CVE-2025-59682. No additional mitigation steps are indicated beyond applying this official fix.

Description

This security update for python-Django addresses two vulnerabilities: a potential SQL injection in several QuerySet methods when used with MySQL and MariaDB, and a potential partial directory traversal vulnerability in the archive.extract() function. Both issues have been fixed to prevent exploitation.

References

Community reviews

Loading reviews…