Homepage

Use of Hard-coded Credentials The advisory has been revoked - it doesn't affect any version of package Django.src  (opens in a new tab)

Threat Intelligence

EPSS
1.85% (84th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-DJANGOSRC-14922777
  • published14 Jan 2026
  • disclosed1 Nov 2016
Report a new vulnerability Found a mistake?

Introduced: 1 Nov 2016

CVE-2016-9013  (opens in a new tab)
CWE-798  (opens in a new tab)

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:10.

NVD Description

Note: Versions mentioned in the description apply only to the upstream Django.src package and not the Django.src package as distributed by RHEL.

Django 1.8.x before 1.8.16, 1.9.x before 1.9.11, and 1.10.x before 1.10.3 use a hardcoded password for a temporary database user created when running tests with an Oracle database, which makes it easier for remote attackers to obtain access to the database server by leveraging failure to manually specify a password in the database settings TEST dictionary.

References