[Snyk] Security upgrade urllib3 from 2.0.7 to 2.5.0

[glenn-jocher]

Snyk has created this PR to fix 2 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:

🦉 Open Redirect

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Security update: Added a specific version requirement for urllib3 to address a vulnerability. 🔒

📊 Key Changes

• Added urllib3>=2.5.0 to the requirements.txt file.
• This change is prompted by Snyk to resolve a known security vulnerability.

🎯 Purpose & Impact

• Ensures the project uses a secure version of urllib3, reducing potential security risks for users.
• No changes to core functionality; this is a behind-the-scenes improvement for safer deployments. 🚀

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting an ultralytics/yolov5 🚀 PR! This is an automated response to help streamline the review process. An Ultralytics engineer will review your contribution and assist you soon.

To ensure a smooth integration, please review the following checklist:

• ✅ Define a Purpose: Make sure the purpose of this update is clearly explained in your PR description, and reference any relevant issues if applicable. Clear, concise commit messages are appreciated!
• ✅ Synchronize with Source: Confirm your PR is up to date with the ultralytics/yolov5 main branch. Use the 'Update branch' button or run git pull and git merge main locally if needed.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks have passed. Please address any failures before requesting review.
• ✅ Update Documentation: If this update affects user-facing features or dependencies, consider updating the documentation as needed.
• ✅ Add Tests: If relevant, include or update tests to cover this change, and ensure all tests pass.
• ✅ Sign the CLA: If this is your first Ultralytics PR, please sign our Contributor License Agreement (CLA) by commenting "I have read the CLA Document and I sign the CLA" below.
• ✅ Minimize Changes: Limit your changes to the minimum required for this update. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

For full details, see our Contributing Guide. If you have any questions or need further assistance, feel free to leave a comment below. Thank you for helping keep Ultralytics projects secure and up to date! 🔒✨