Skip to main content
VulnerabilityPublished

CVE-2026-53878: djangoproject Django · Improper Neutralization of Line Delimiters

Affects djangoproject DjangoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.1 Medium : upgrade to 6.0.7 or 5.2.16 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.0.7, 5.2.16
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jul 2026

  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 17 Nov 2026.

What to do

Upgrade Django and django to 6.0.7 or 5.2.16.

Affected software

ProductAffectedFixed in
djangoprojectDjangoAffected
  • >=6.0 <6.0.7
Fixed in
  • 6.0.7
djangoprojectDjangoAffected
  • >=5.2 <5.2.16
Fixed in
  • 5.2.16
PyPIdjangopkg:pypi/djangoOther threatsAffected
  • >=6.0 <6.0.7
  • >=5.2 <5.2.16
Fixed in
  • 6.0.7
  • 5.2.16

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

AI-suggested

A patch is available in Django versions 6.0.7 and 5.2.16 that addresses this issue by properly prohibiting newlines in domain names validated by DomainNameValidator. Users should upgrade to these or later versions to remediate the vulnerability. Since Django's HttpResponse class already prevents newlines in headers, applications using standard Django response handling are not directly vulnerable. No additional mitigation is required beyond applying the official patch.

Description

An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16. `DomainNameValidator` does not prohibit newlines in domain names (unless used via a form field, since `CharField` strips newlines). If an application uses values with newlines in an HTTP response, header injection can occur. Django itself is unaffected because `HttpResponse` prohibits newlines in HTTP headers. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Bence Nagy for reporting this issue.

References

Community reviews

Loading reviews…