[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

Added a security update by specifying a minimum version for the urllib3 library in the requirements.

📊 Key Changes

• Added urllib3>=2.5.0 to the requirements.txt file to address a known security vulnerability.

🎯 Purpose & Impact

• 🛡️ Improves project security by ensuring a safe version of urllib3 is used.
• 🔒 Helps users avoid potential security risks flagged by automated tools like Snyk.
• 🚀 No impact on features or user experience—purely a behind-the-scenes safety improvement.

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting an ultralytics/yolov3 🚀 PR! This is an automated response to help streamline the process—a member of the Ultralytics team will review and assist you soon.

Please review the checklist below to ensure a smooth integration:

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and follow the project's conventions.
• ✅ Synchronize with Source: Make sure your PR is up-to-date with the ultralytics/yolov3 main branch. If needed, use the 'Update branch' button or run git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Confirm all Ultralytics Continuous Integration (CI) checks are passing. Please resolve any failing checks.
• ✅ Update Documentation: If your changes affect functionality, update the documentation accordingly.
• ✅ Add Tests: Where applicable, include or update tests to cover your changes, and verify that all tests are passing.
• ✅ Sign the CLA: If this is your first Ultralytics PR, please sign our Contributor License Agreement by commenting "I have read the CLA Document and I sign the CLA" in this PR.
• ✅ Minimize Changes: Limit the scope of your changes to only what's necessary for your fix or feature. "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 further details, please see our Contributing Guide. If you have any questions, feel free to leave a comment.

Thank you for helping keep Ultralytics secure and robust! 🛡️✨