[Snyk] Security upgrade tensorflow from 1.2.1 to 2.5.0 #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296571
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296572
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296573
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296574
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 6.3
SNYK-PYTHON-TENSORFLOW-1296575
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 4.4
SNYK-PYTHON-TENSORFLOW-1296576
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296577
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296578
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296579
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296580
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 7.3
SNYK-PYTHON-TENSORFLOW-1296581
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296582
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296583
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296584
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296585
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296586
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296587
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296588
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 7.1
SNYK-PYTHON-TENSORFLOW-1296589
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 7.1
SNYK-PYTHON-TENSORFLOW-1296590
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296591
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296592
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296595
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296598
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296601
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296610
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 3.6
SNYK-PYTHON-TENSORFLOW-1296613
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296616
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296619
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296622
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296625
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 3.6
SNYK-PYTHON-TENSORFLOW-1296628
tensorflow:
1.2.1 -> 2.5.0
Why? Recently disclosed, Has a fix available, CVSS 2.5
SNYK-PYTHON-TENSORFLOW-1296631
tensorflow:
1.2.1 -> 2.5.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