[Snyk] Security upgrade tornado from 5.1.1 to 6.3.3

[Naveen25697]

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:
  • Workflow5/workflow5_requirements.txt

⚠️ Warning

requests 2.21.0 has requirement urllib3<1.25,>=1.21.1, but you have urllib3 2.0.7.
notebook 6.5.6 has requirement terminado>=0.8.3, but you have terminado 0.8.1.
notebook 6.5.6 has requirement jupyter-core>=4.6.1, but you have jupyter-core 4.4.0.
notebook 6.5.6 has requirement Send2Trash>=1.8.0, but you have Send2Trash 1.5.0.
notebook 6.5.6 has requirement jupyter-client<8,>=5.3.4, but you have jupyter-client 5.2.4.
nbclassic 1.0.0 has requirement terminado>=0.8.3, but you have terminado 0.8.1.
nbclassic 1.0.0 has requirement jupyter-client>=6.1.1, but you have jupyter-client 5.2.4.
nbclassic 1.0.0 has requirement jupyter-core>=4.6.1, but you have jupyter-core 4.4.0.
nbclassic 1.0.0 has requirement Send2Trash>=1.8.0, but you have Send2Trash 1.5.0.
jupyter-server 1.24.0 has requirement jupyter-core!=5.0.*,>=4.12, but you have jupyter-core 4.4.0.
jupyter-server 1.24.0 has requirement jupyter-client>=6.1.12, but you have jupyter-client 5.2.4.
jupyter-server 1.24.0 has requirement terminado>=0.8.3, but you have terminado 0.8.1.
jupyter-server 1.24.0 has requirement traitlets>=5.1, but you have traitlets 4.3.2.
jupyter-server 1.24.0 has requirement nbconvert>=6.4.4, but you have nbconvert 5.4.0.
jupyter-server 1.24.0 has requirement nbformat>=5.2.0, but you have nbformat 4.4.0.
Jinja2 3.1.2 has requirement MarkupSafe>=2.0, but you have MarkupSafe 1.1.0.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	611/1000 Why? Recently disclosed, Has a fix available, CVSS 6.5	HTTP Request Smuggling SNYK-PYTHON-TORNADO-6041512	tornado: 5.1.1 -> 6.3.3	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:
🧐 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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.