(*) 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
Vulnerabilities that will be fixed
By pinning:
Why? Has a fix available, CVSS 3.8
SNYK-PYTHON-LOGURU-2351960
loguru:0.5.3 -> 0.6.0Why? Has a fix available, CVSS 5.7
SNYK-PYTHON-PROTOBUF-3031740
protobuf:3.19.1 -> 3.19.5Why? Proof of Concept exploit, Has a fix available, CVSS 7.4
SNYK-PYTHON-PYJWT-2840625
pyjwt:2.3.0 -> 2.4.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 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:
š¦ Arbitrary Code Injection š¦ Use of a Broken or Risky Cryptographic Algorithm