CVE-2026-53878: django — Fix

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.

Is your site exposed to CVE-2026-53878?

Run a free security scan — no signup, results in seconds.

CVSS v3.1 Score

6.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS — Exploit Prediction

0.0022

Probability of exploitation

0.12%

Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

Weakness Type (CWE)

CWE-144 CWE-144

Affected Products

Vendor	Product	Versions
djangoproject	django	5.2 — 5.2.16
djangoproject	django	6.0 — 6.0.7

References

Advisories & Patches

https://docs.djangoproject.com/en/dev/releases/security/ https://www.djangoproject.com/weblog/2026/jul/07/security-releases/

Other References

https://groups.google.com/g/django-announce

Frequently Asked Questions

What is CVE-2026-53878? +

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. It has a CVSS v3.1 base score of 6.1 (MEDIUM).

How severe is CVE-2026-53878? +

CVE-2026-53878 has a CVSS v3.1 score of 6.1 out of 10, rated MEDIUM. This is a medium-severity vulnerability that should be remediated as part of regular maintenance. The EPSS score is 0.0022, placing it in the 0th percentile for exploitation probability.

What products are affected by CVE-2026-53878? +

CVE-2026-53878 affects products from djangoproject, specifically: django. Check the affected products table above for specific version ranges.

How do I check if I'm vulnerable to CVE-2026-53878? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.

Related Vulnerabilities

CVE-2025-24367 8.8

Cacti is an open source performance and fault management framework. An authenticated Cacti user can abuse graph creation and graph …

CVE-2024-53908 9.8

An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. Direct usage of the …

CVE-2025-64459 9.1

An issue was discovered in 5.1 before 5.1.14, 4.2 before 4.2.26, and 5.2 before 5.2.8. The methods `QuerySet.filter()`, `QuerySet.exclude()`, and …

CVE-2025-64458 7.5

An issue was discovered in 5.1 before 5.1.14, 4.2 before 4.2.26, and 5.2 before 5.2.8. NFKC normalization in Python is …

CVE-2024-53907 7.5

An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. The strip_tags() method and …

CVE-2025-64460 7.5

An issue was discovered in 5.2 before 5.2.9, 5.1 before 5.1.15, and 4.2 before 4.2.27. Algorithmic complexity in `django.core.serializers.xml_serializer.getInnerText()` allows …

CVE-2026-53878