EUVD-2026-42045
GHSA-8qcx-xf44-272x
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
AC:H reflects the non-default application pattern required - direct DomainNameValidator use bypassing both CharField and HttpResponse protections; remaining metrics mirror standard header injection impact.
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Primary rating from Vendor (DSF).
CVSS VectorVendor: DSF
Lifecycle Timeline
3Blast Radius
ecosystem impact- 12 pypi packages depend on django (12 direct, 0 indirect)
Ecosystem-wide dependent count for version 5.2.
DescriptionCVE.org
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.
AnalysisAI
Header injection in Django's DomainNameValidator allows network attackers to inject arbitrary HTTP response headers when applications pass validator-accepted domain values directly into HTTP responses, affecting Django 6.0 before 6.0.7 and 5.2 before 5.2.16. The validator silently accepts embedded newline characters in domain name strings, enabling HTTP response splitting that can facilitate session hijacking, open redirects, or cross-site scripting against end users. No public exploit code or CISA KEV listing exists at time of analysis; practical risk is narrowed significantly by Django's HttpResponse class independently rejecting newlines, meaning only non-standard code paths are exploitable.
Technical ContextAI
The root cause is CWE-144 (Improper Neutralization of Line Delimiters): Django's DomainNameValidator fails to reject or strip CRLF (\r\n) and LF (\n) characters from domain name inputs. In HTTP/1.1, headers are delimited by CRLF sequences, so injecting newlines into a header value allows an attacker to terminate the current header and append entirely new ones - a technique known as HTTP response splitting. The affected CPE cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:* spans all Django versions in the 5.2 and 6.0 series. Two independent safeguards exist in the standard stack that limit exposure: Django's CharField.clean() strips newlines before passing values to the validator (protecting form-based flows), and Django's HttpResponse API independently rejects newlines when setting headers. The vulnerability surfaces only when DomainNameValidator is invoked outside of a form field AND its output is written to a response header through a raw WSGI/ASGI path that bypasses HttpResponse's own sanitization guard.
RemediationAI
Upgrade to Django 6.0.7 or Django 5.2.16, released by the Django Software Foundation on 2026-07-07 and documented at https://www.djangoproject.com/weblog/2026/jul/07/security-releases/. For deployments that cannot patch immediately, audit all code paths where DomainNameValidator (or model fields that invoke it) is called directly on user-supplied input and the result is subsequently written to an HTTP response header outside of Django's HttpResponse or HttpResponseBase APIs - these are the only exploitable patterns. A targeted compensating control is to add explicit newline stripping before any user-influenced string is placed in a header value (e.g., value.replace('\r', '').replace('\n', '')); note this addresses the symptom rather than the root cause and should not substitute for patching. Avoid relying on unsupported Django series (5.0.x and earlier) in production environments, as those branches have not been assessed and carry no committed patch path.
Wazuh SIEM platform versions 4.4.0 through 4.9.0 contain an unsafe deserialization vulnerability in the DistributedAPI t
BentoML version 1.4.2 and earlier contains an unauthenticated remote code execution vulnerability through insecure deser
pgAdmin 4 contains critical remote code execution vulnerabilities in the Query Tool download and Cloud Deployment endpoi
The renderLocalView function in render/views.py in graphite-web in Graphite 0.9.5 through 0.9.10 uses the pickle Python
BentoML is a Python library for building online serving systems optimized for AI apps and model inference. Rated critica
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
pyLoad download manager version prior to 0.5.0b3.dev77 exposes the Flask SECRET_KEY through an unauthenticated endpoint.
Langflow (a visual LLM pipeline builder) contains a critical unauthenticated code execution vulnerability (CVE-2026-3301
In Mercurial before 4.1.3, "hg serve --stdio" allows remote authenticated users to launch the Python debugger, and conse
Unauthenticated remote code execution in Marimo ≤0.20.4 allows attackers to execute arbitrary system commands via the `/
pyLoad is the free and open-source Download Manager written in pure Python. Rated medium severity (CVSS 5.3), this vulne
Cross-user flow execution in Langflow (< 1.9.1) lets any authenticated API-key holder run another user's flow by passing
Same weakness CWE-144 – Improper Neutralization of Line Delimiters
View allSame technique Code Injection
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Linux Enterprise Module for Package Hub 15 SP7 | Not-Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | Not-Affected |
| openSUSE Leap 15.6 | Not-Affected |
Share
External POC / Exploit Code
Leaving vuln.today