[Snyk] Security upgrade aiohttp from 3.8.6 to 3.9.2

[sumanth-lingappa]

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:
  • requirements.txt

⚠️ Warning

sphinx 5.3.0 has requirement docutils<0.20,>=0.14, but you have docutils 0.20.1.
rstcheck 6.1.2 has requirement importlib-metadata<5.0,>=1.6; python_version < "3.8", but you have importlib-metadata 6.7.0.
rstcheck-core 1.0.3 has requirement docutils<0.20,>=0.7, but you have docutils 0.20.1.
rstcheck-core 1.0.3 has requirement importlib-metadata<5.0,>=1.6; python_version < "3.8", but you have importlib-metadata 6.7.0.
galaxy-importer 0.5.0 requires ansible-lint, which is not installed.
galaxy-importer 0.5.0 requires ansible-core, which is not installed.
flake8 5.0.4 has requirement importlib-metadata<4.3,>=1.1.0; python_version < "3.8", but you have importlib-metadata 6.7.0.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	591/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 5.4	Improper Input Validation SNYK-PYTHON-AIOHTTP-6091621	aiohttp: 3.8.6 -> 3.9.2	No	Proof of Concept
	591/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 5.4	Improper Input Validation SNYK-PYTHON-AIOHTTP-6091622	aiohttp: 3.8.6 -> 3.9.2	No	Proof of Concept
	616/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 5.9	Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') SNYK-PYTHON-AIOHTTP-6209406	aiohttp: 3.8.6 -> 3.9.2	No	Proof of Concept
	646/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 6.5	HTTP Request Smuggling SNYK-PYTHON-AIOHTTP-6209407	aiohttp: 3.8.6 -> 3.9.2	No	Proof of Concept

(*) 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:

🦉 Improper Input Validation
🦉 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}