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
```
Scrapy 1.8.1 requires Twisted, which is not installed.
Scrapy 1.8.1 has requirement parsel>=1.5.0, but you have parsel 1.4.0.
requests 2.20.0 has requirement urllib3<1.25,>=1.21.1, but you have urllib3 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 effected 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
``` Scrapy 1.8.1 requires Twisted, which is not installed. Scrapy 1.8.1 has requirement parsel>=1.5.0, but you have parsel 1.4.0. requests 2.20.0 has requirement urllib3<1.25,>=1.21.1, but you have urllib3 1.26.5. ```Vulnerabilities that will be fixed
By pinning:
Why? Has a fix available, CVSS 7.5
SNYK-PYTHON-CRYPTOGRAPHY-1022152
cryptography:
2.3.1 -> 3.2
Why? Has a fix available, CVSS 7.5
SNYK-PYTHON-FLASKCORS-608972
flask-cors:
3.0.4 -> 3.0.9
Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
SNYK-PYTHON-JINJA2-1012994
jinja2:
2.10 -> 2.11.3
Why? Has a fix available, CVSS 6
SNYK-PYTHON-JINJA2-174126
jinja2:
2.10 -> 2.11.3
Why? Has a fix available, CVSS 7.3
SNYK-PYTHON-LXML-1047473
lxml:
4.2.1 -> 4.6.5
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-LXML-1047474
lxml:
4.2.1 -> 4.6.5
Why? Has a fix available, CVSS 6.3
SNYK-PYTHON-LXML-1088006
lxml:
4.2.1 -> 4.6.5
Why? Recently disclosed, Has a fix available, CVSS 8.2
SNYK-PYTHON-LXML-2316995
lxml:
4.2.1 -> 4.6.5
Why? Has a fix available, CVSS 6.5
SNYK-PYTHON-LXML-72651
lxml:
4.2.1 -> 4.6.5
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 3.7
SNYK-PYTHON-NUMPY-2321969
numpy:
1.15.2 -> 1.22.0rc1
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 3.7
SNYK-PYTHON-NUMPY-2321970
numpy:
1.15.2 -> 1.22.0rc1
Why? Proof of Concept exploit, Has a fix available, CVSS 9.8
SNYK-PYTHON-NUMPY-73513
numpy:
1.15.2 -> 1.22.0rc1
Why? Proof of Concept exploit, Has a fix available, CVSS 4.3
SNYK-PYTHON-PY-1049546
py:
1.5.3 -> 1.10.0
Why? Has a fix available, CVSS 5.7
SNYK-PYTHON-SCRAPY-1729576
scrapy:
1.5.0 -> 1.8.1
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-URLLIB3-1533435
urllib3:
1.25.9 -> 1.26.5
Why? Has a fix available, CVSS 9.1
SNYK-PYTHON-WERKZEUG-458931
werkzeug:
0.14.1 -> 0.15.3
(*) 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 effected 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