| | 296 | === Close duplicate (untriaged) report === |
| | 297 | Thank you for your report. |
| | 298 | |
| | 299 | This potential issue has previously been reported to the Django Security |
| | 300 | Team and is currently under assessment. We have not yet determined whether |
| | 301 | it constitutes a security vulnerability. In the meantime, please keep this |
| | 302 | information confidential. |
| | 303 | |
| | 304 | Our policy is to coordinate with the original reporter to reduce the |
| | 305 | administrative work required of our volunteer open source team. As a |
| | 306 | result, you may not receive further updates or be notified of the outcome. |
| | 307 | |
| | 308 | Assessment can take several weeks. Please only follow up if you discover |
| | 309 | new, relevant information. We aim to complete our assessment within 90 days |
| | 310 | of the original report. |
| | 311 | |
| | 312 | Kind regards, |
| | 313 | The Django Security Team |
| | 314 | |