[Snyk] Fix for 5 vulnerabilities

[glenn-jocher]

Snyk has created this PR to fix 5 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• requirements.txt

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• 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.

---

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Improper Control of Generation of Code ('Code Injection')
🦉 Use After Free

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Updated software requirements to improve compatibility and security. 🛠️✨

📊 Key Changes

• Increased the minimum PyTorch version from 1.8.0 to 2.2.0. 🚀
• Added a new pinned requirement for wheel (>=0.38.0) to mitigate a security vulnerability. 🔒

🎯 Purpose & Impact

• Enhanced Compatibility: Upgrading PyTorch ensures support for newer features and better performance optimizations inherent in the latest versions. 🤖⚡
• Improved Security: Pinning wheel to a secure version addresses a known vulnerability, enhancing project safety and stability for users. 🛡️
• User Update Required: Users must update PyTorch and ensure they meet the new minimum requirements to avoid potential compatibility issues. 🔄

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/yolov3 🚀 pull request (PR)! This is an automated response to help guide your contributions and ensure a smooth review process. An Ultralytics engineer will review your PR soon. Meanwhile, please ensure the following checklist is completed:

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in the PR description. Link any relevant issues to provide additional context.
• ✅ Synchronize with Source: Make sure your PR branch is up-to-date with the main branch of ultralytics/yolov3. You can update by clicking the 'Update branch' button or running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify that all Continuous Integration (CI) checks pass to avoid delays in the review process. If there are any failures, please address them.
• ✅ Update Documentation: If your changes impact functionality or introduce new features, update the documentation accordingly.
• ✅ Add Tests: Include or update tests where applicable to ensure your changes are thoroughly validated. Confirm that all tests succeed with your modifications.
• ✅ Sign the CLA: If this is your first contribution to Ultralytics, please sign our Contributor License Agreement (CLA) by stating:
  "I have read the CLA Document and I sign the CLA" in the PR comments.
• ✅ Minimize Changes: Verify that your changes are limited to what’s essential for this PR. Follow the principle: "Hack away the unessential."

If this PR addresses vulnerabilities, please ensure all changes resolve the intended issues without introducing regressions. For additional guidance, check out our Contributing Guide.

Don’t hesitate to leave a comment if you have questions or need further assistance. Thank you for contributing to Ultralytics! 🚀🙏