Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR
Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
requirements.txt
⚠️ Warning
```
requests 2.24.0 has requirement urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1, but you have urllib3 1.26.5.
pytest-cov 2.10.1 requires coverage, which is not installed.
importlib-metadata 2.0.0 requires zipp, which is not installed.
drf-yasg 1.17.1 requires ruamel.yaml, which is not installed.
drf-yasg 1.17.1 requires inflection, which is not installed.
django-graphql-jwt 0.3.1 requires PyJWT, which is not installed.
beautifulsoup4 4.9.1 requires soupsieve, which is not installed.
beautifulsoup4 4.9.1 requires soupsieve, which is not installed.
```
(*) 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
``` requests 2.24.0 has requirement urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1, but you have urllib3 1.26.5. pytest-cov 2.10.1 requires coverage, which is not installed. importlib-metadata 2.0.0 requires zipp, which is not installed. drf-yasg 1.17.1 requires ruamel.yaml, which is not installed. drf-yasg 1.17.1 requires inflection, which is not installed. django-graphql-jwt 0.3.1 requires PyJWT, which is not installed. beautifulsoup4 4.9.1 requires soupsieve, which is not installed. beautifulsoup4 4.9.1 requires soupsieve, which is not installed. ```Vulnerabilities that will be fixed
By pinning:
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-2312875
django:
3.1.13 -> 3.2.15
Why? Has a fix available, CVSS 3.7
SNYK-PYTHON-DJANGO-2329158
django:
3.1.13 -> 3.2.15
Why? Has a fix available, CVSS 3.7
SNYK-PYTHON-DJANGO-2329159
django:
3.1.13 -> 3.2.15
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-2329160
django:
3.1.13 -> 3.2.15
Why? Has a fix available, CVSS 4.2
SNYK-PYTHON-DJANGO-2389002
django:
3.1.13 -> 3.2.15
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-2389021
django:
3.1.13 -> 3.2.15
Why? Has a fix available, CVSS 8.2
SNYK-PYTHON-DJANGO-2606966
django:
3.1.13 -> 3.2.15
Why? Proof of Concept exploit, Has a fix available, CVSS 8.2
SNYK-PYTHON-DJANGO-2606969
django:
3.1.13 -> 3.2.15
Why? Proof of Concept exploit, Has a fix available, CVSS 9.1
SNYK-PYTHON-DJANGO-2940618
django:
3.1.13 -> 3.2.15
Why? Has a fix available, CVSS 7
SNYK-PYTHON-DJANGO-2968205
django:
3.1.13 -> 3.2.15
Why? Proof of Concept exploit, Has a fix available, CVSS 7.4
SNYK-PYTHON-PYJWT-2840625
pyjwt:
1.7.1 -> 2.4.0
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-URLLIB3-1533435
urllib3:
1.25.11 -> 1.26.5
(*) 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:
🦉 Access Restriction Bypass 🦉 Directory Traversal 🦉 Denial of Service (DoS) 🦉 More lessons are available in Snyk Learn