All reports
Critical

Django DNS Rebinding Vulnerability

Affected versions

Version ranges need review.

Affected versions
>= 1.9a1, < 1.9.11
Fixed version
1.9.11
Affected versions
>= 1.10a1, < 1.10.3
Fixed version
1.10.3
Affected versions
>= 1.8a1, < 1.8.16
Fixed version
1.8.16
Affected versions
<1.8.16 || >=1.9 <1.9.11 || >=1.10 <1.10.3
Fixed version
1.10.3 · 1.8.16 · 1.9.11
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2016-9014

Probability of exploitation in the next 30 days: 6.07%

FIRST EPSS · 2026-11-19

Description

Django before 1.8.x before 1.8.16, 1.9.x before 1.9.11, and 1.10.x before 1.10.3, when settings.DEBUG is True, allow remote attackers to conduct DNS rebinding attacks by leveraging failure to validate the HTTP Host header against settings.ALLOWED_HOSTS.

Links

Credits

  • MarkLee131