(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.
Note:You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR
⚠️ Warning
``` ipython 5.3.0 requires simplegeneric, which is not installed. django-rq 0.9.1 requires django, which is not installed. ```Vulnerabilities that will be fixed
By pinning:
Why? Has a fix available, CVSS 3.1
SNYK-PYTHON-DJANGO-1066259
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 3.3
SNYK-PYTHON-DJANGO-1279042
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 7.3
SNYK-PYTHON-DJANGO-1290072
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 7.5
SNYK-PYTHON-DJANGO-1298665
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 5.9
SNYK-PYTHON-DJANGO-173679
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 2.4
SNYK-PYTHON-DJANGO-174885
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-2312875
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 3.7
SNYK-PYTHON-DJANGO-2329158
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 3.7
SNYK-PYTHON-DJANGO-2329159
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-2329160
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 4.2
SNYK-PYTHON-DJANGO-2389002
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-2389021
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 8.2
SNYK-PYTHON-DJANGO-2606966
django:
1.11 -> 3.2.15
Why? Proof of Concept exploit, Has a fix available, CVSS 8.2
SNYK-PYTHON-DJANGO-2606969
django:
1.11 -> 3.2.15
Why? Proof of Concept exploit, Has a fix available, CVSS 9.1
SNYK-PYTHON-DJANGO-2940618
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 7
SNYK-PYTHON-DJANGO-2968205
django:
1.11 -> 3.2.15
Why? Proof of Concept exploit, Has a fix available, CVSS 6.1
SNYK-PYTHON-DJANGO-40626
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-40778
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-40779
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 6.1
SNYK-PYTHON-DJANGO-42178
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 7.3
SNYK-PYTHON-DJANGO-451300
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-456540
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-456541
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-456542
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-456566
django:
1.11 -> 3.2.15
Why? Mature exploit, Has a fix available, CVSS 5.9
SNYK-PYTHON-DJANGO-538244
django:
1.11 -> 3.2.15
Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
SNYK-PYTHON-DJANGO-543998
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 7.6
SNYK-PYTHON-DJANGO-559326
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 4.3
SNYK-PYTHON-DJANGO-72888
django:
1.11 -> 3.2.15
Why? Has a fix available, CVSS 7.3
SNYK-PYTHON-LXML-1047473
lxml:
3.6.0 -> 4.9.1
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-LXML-1047474
lxml:
3.6.0 -> 4.9.1
Why? Has a fix available, CVSS 6.3
SNYK-PYTHON-LXML-1088006
lxml:
3.6.0 -> 4.9.1
Why? Has a fix available, CVSS 8.2
SNYK-PYTHON-LXML-2316995
lxml:
3.6.0 -> 4.9.1
Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
SNYK-PYTHON-LXML-2940874
lxml:
3.6.0 -> 4.9.1
Why? Has a fix available, CVSS 6.5
SNYK-PYTHON-LXML-72651
lxml:
3.6.0 -> 4.9.1
(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information: 🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Directory Traversal 🦉 Directory Traversal 🦉 Directory Traversal 🦉 More lessons are available in Snyk Learn