Skip to main content
CVE-2025-48432VulnerabilityPublished Updated

SUSE · Security update for python-Django

Affects SUSESource GCVE Database

0
Compare
Authoritative record:CVE-2025-48432· Medium 4.0

Not known to be exploited · CVSS 4.0 Medium · fixed in SUSE package updates : update SUSE django when convenient.

Data as of 15 Nov 2026, 22:49 UTC

CVSS 3.1 base score
4.0Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 5.2.3, 5.1.11, 4.2.23
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jun 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

Upgrade django to 5.2.3, 5.1.11 or 4.2.23.

Affected software

ProductAffectedFixed in
PyPIdjangopkg:pypi/djangoOther threatsAffected
  • <4.2.23
  • <5.1.11
  • <5.2.3
Fixed in
  • 4.2.23
  • 5.1.11
  • 5.2.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

This update for python-Django fixes the following issues: - CVE-2025-48432: log injection or forgery due to unescaped control characters being added into logs (bsc#1244095).

References

Community reviews

Loading reviews…