(*) 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
``` tensorboard 1.14.0 has requirement setuptools>=41.0.0, but you have setuptools 39.0.1. ```Vulnerabilities that will be fixed
By pinning:
Why? Recently disclosed, Has a fix available, CVSS 3.4
SNYK-PYTHON-TENSORFLOW-1013444
tensorflow:
1.14.0 -> 1.15.4
Why? Recently disclosed, Has a fix available, CVSS 7.5
SNYK-PYTHON-TENSORFLOW-1013450
tensorflow:
1.14.0 -> 1.15.4
Why? Recently disclosed, Has a fix available, CVSS 6.5
SNYK-PYTHON-TENSORFLOW-1013452
tensorflow:
1.14.0 -> 1.15.4
Why? Recently disclosed, Has a fix available, CVSS 7.5
SNYK-PYTHON-TENSORFLOW-1013496
tensorflow:
1.14.0 -> 1.15.4
Why? Recently disclosed, Has a fix available, CVSS 7.4
SNYK-PYTHON-TENSORFLOW-1013502
tensorflow:
1.14.0 -> 1.15.4
Why? Recently disclosed, Has a fix available, CVSS 5.3
SNYK-PYTHON-TENSORFLOW-1013538
tensorflow:
1.14.0 -> 1.15.4
Why? Recently disclosed, Has a fix available, CVSS 8.1
SNYK-PYTHON-TENSORFLOW-1013542
tensorflow:
1.14.0 -> 1.15.4
Why? Recently disclosed, Has a fix available, CVSS 9
SNYK-PYTHON-TENSORFLOW-1013547
tensorflow:
1.14.0 -> 1.15.4
Why? Recently disclosed, Has a fix available, CVSS 7.4
SNYK-PYTHON-TENSORFLOW-1013548
tensorflow:
1.14.0 -> 1.15.4
(*) 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