berndverst
commented
3 months ago @caniszczyk could you please sign your commit? Otherwise I'll have to close your PR and manually make the change as myself.
- In your local branch, run:
git rebase HEAD~1 --signoff - Force push your changes to overwrite the branch:
git push --force-with-lease origin snyk-fix-799147f133b5a9300fde88fe1ec75b15
This PR was automatically created by Snyk using the credentials of a real user.
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: - examples/workflow/requirements.txt #### Vulnerabilities that will be fixed ##### By pinning: Severity | Priority Score (*) | Issue | Upgrade | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:-------------------------|:-------------------------  | **521/1000****Why?** Recently disclosed, Has a fix available, CVSS 4.7 | Cross-site Scripting (XSS)
[SNYK-PYTHON-AIOHTTP-6645291](https://snyk.io/vuln/SNYK-PYTHON-AIOHTTP-6645291) | `aiohttp:`
`3.8.6 -> 3.9.4`
| No | No Known Exploit (*) 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: