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:
unbrake-api/production/requirements.txt
⚠️ Warning
```
graphql-relay 0.5.0 has requirement graphql-core<2,>=0.5.0, but you have graphql-core 2.3.2.
graphene-django 2.15.0 has requirement graphene<3,>=2.1.7, but you have graphene 2.1.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.
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
``` graphql-relay 0.5.0 has requirement graphql-core<2,>=0.5.0, but you have graphql-core 2.3.2. graphene-django 2.15.0 has requirement graphene<3,>=2.1.7, but you have graphene 2.1.3. ```Vulnerabilities that will be fixed
By pinning:
Why? Has a fix available, CVSS 3.1
SNYK-PYTHON-DJANGO-1066259
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 5.9
SNYK-PYTHON-DJANGO-1076802
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 3.7
SNYK-PYTHON-DJANGO-1090612
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 3.3
SNYK-PYTHON-DJANGO-1279042
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 7.3
SNYK-PYTHON-DJANGO-1290072
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 7.5
SNYK-PYTHON-DJANGO-1298665
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 4.3
SNYK-PYTHON-DJANGO-1298666
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-2312875
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 3.7
SNYK-PYTHON-DJANGO-2329158
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 3.7
SNYK-PYTHON-DJANGO-2329159
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-2329160
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 4.2
SNYK-PYTHON-DJANGO-2389002
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-2389021
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 7.3
SNYK-PYTHON-DJANGO-451300
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-456540
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-456541
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-456542
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-456566
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 6.3
SNYK-PYTHON-DJANGO-536439
django:
2.2.2 -> 2.2.27
Why? Proof of Concept exploit, Has a fix available, CVSS 5.9
SNYK-PYTHON-DJANGO-538244
django:
2.2.2 -> 2.2.27
Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
SNYK-PYTHON-DJANGO-543998
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 7.6
SNYK-PYTHON-DJANGO-559326
django:
2.2.2 -> 2.2.27
Why? Proof of Concept exploit, Has a fix available, CVSS 5.9
SNYK-PYTHON-DJANGO-571013
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 6.5
SNYK-PYTHON-DJANGO-571014
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 7.3
SNYK-PYTHON-DJANGO-609368
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 8.4
SNYK-PYTHON-DJANGO-609369
django:
2.2.2 -> 2.2.27
Why? Has a fix available, CVSS 3.1
SNYK-PYTHON-DJANGOCORSHEADERS-564347
django-cors-headers:
2.5.2 -> 3.0.0
Why? Has a fix available, CVSS 7.5
SNYK-PYTHON-EMITTERIO-570768
emitter-io:
2.0.2 -> 2.704
Why? Has a fix available, CVSS 5.6
SNYK-PYTHON-GUNICORN-541164
gunicorn:
19.9.0 -> 19.10.0
(*) 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
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Directory Traversal 🦉 Directory Traversal 🦉 Directory Traversal 🦉 More lessons are available in Snyk Learn