[Snyk] Security upgrade urllib3 from 1.23 to 2.5.0

[naiba4]

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

Snyk changed the following file(s):

• requirements.txt

⚠️ Warning

equests 2.19.1 requires urllib3, which is not installed.

---

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: df2ae71

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[guardrails]

⚠️ We detected 3 security issues in this pull request:

Vulnerable Libraries (3)

Severity	Details
High	pkg:pypi/babel@2.6.0 (t) upgrade to: 2.9.1
Medium	pkg:pypi/jinja2@2.10 (t) upgrade to: 2.11.3
Medium	pkg:pypi/pygments@2.2.0 (t) upgrade to: 2.15.1

More info on how to fix Vulnerable Libraries in Python.

---

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	urllib3@​1.23 ⏵ 2.5.0	+1

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Block		colorama@0.4.6 has Shell access. Location: Package overview From: ? → pypi/sphinx@8.2.3 → pypi/urllib3@2.5.0 → pypi/colorama@0.4.6 ℹ Read more on: This package | This alert | What is shell access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/colorama@0.4.6. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		cryptography@45.0.4 has Shell access. Location: Package overview From: ? → pypi/requests@2.19.1 → pypi/urllib3@2.5.0 → pypi/cryptography@45.0.4 ℹ Read more on: This package | This alert | What is shell access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/cryptography@45.0.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		cryptography@45.0.4 has Network access. Location: Package overview From: ? → pypi/requests@2.19.1 → pypi/urllib3@2.5.0 → pypi/cryptography@45.0.4 ℹ Read more on: This package | This alert | What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/cryptography@45.0.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		cryptography@45.0.4 Uses eval. Location: Package overview From: ? → pypi/requests@2.19.1 → pypi/urllib3@2.5.0 → pypi/cryptography@45.0.4 ℹ Read more on: This package | This alert | What is dynamic code execution? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/cryptography@45.0.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		cryptography@45.0.4 has Native code. Location: Package overview From: ? → pypi/requests@2.19.1 → pypi/urllib3@2.5.0 → pypi/cryptography@45.0.4 ℹ Read more on: This package | This alert | Why is native code a concern? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Verify that the inclusion of native code is expected and necessary for this package's functionality. If it is unnecessary or unexpected, consider using alternative packages without native code to mitigate potential risks. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/cryptography@45.0.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		pysocks@1.7.1 has Network access. Location: Package overview From: ? → pypi/requests@2.19.1 → pypi/urllib3@2.5.0 → pypi/pysocks@1.7.1 ℹ Read more on: This package | This alert | What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pysocks@1.7.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		pysocks@1.7.1 has Native code. Location: Package overview From: ? → pypi/requests@2.19.1 → pypi/urllib3@2.5.0 → pypi/pysocks@1.7.1 ℹ Read more on: This package | This alert | Why is native code a concern? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Verify that the inclusion of native code is expected and necessary for this package's functionality. If it is unnecessary or unexpected, consider using alternative packages without native code to mitigate potential risks. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pysocks@1.7.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		pysocks@1.7.1 has Shell access. Location: Package overview From: ? → pypi/requests@2.19.1 → pypi/urllib3@2.5.0 → pypi/pysocks@1.7.1 ℹ Read more on: This package | This alert | What is shell access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pysocks@1.7.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		urllib3@2.5.0 has Shell access. Location: Package overview From: requirements.txt → pypi/urllib3@2.5.0 ℹ Read more on: This package | This alert | What is shell access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/urllib3@2.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		colorama@0.4.6 has URL strings. URLs: http://en.wikipedia.org/wiki/ANSI_escape_code Location: Package overview From: ? → pypi/sphinx@8.2.3 → pypi/urllib3@2.5.0 → pypi/colorama@0.4.6 ℹ Read more on: This package | This alert | What are URL strings? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/colorama@0.4.6. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		cryptography@45.0.4 has Environment variable access. Location: Package overview From: ? → pypi/requests@2.19.1 → pypi/urllib3@2.5.0 → pypi/cryptography@45.0.4 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/cryptography@45.0.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		cryptography@45.0.4 has URL strings. URLs: https://github.com/pyca/cryptography/blob/%s/src/cryptography/%s%s, https://docs.python.org/3, https://info.isl.ntt.co.jp/crypt/eng/camellia/, https://speakerdeck.com, https://stackoverflow.com, https://webstore.ansi.org, https://github.com/, https://www.cosic.esat.kuleuven.be, https://wiki.sei.cmu.edu, https://chromium.googlesource.com/chromium/src/+/refs/heads/main/base, https://github.com/pyca/pyopenssl/issues/1031, https://github.com/pyca/cryptography/, https://datatracker.ietf.org/doc/html/rfc5246#section-7.4.1.4.1, https://github.com/pyca/cryptography/issues/5872, https://tools.ietf.org/html/rfc1321, https://github.com/pyca/cryptography/issues/2557, https://cryptography.io, http://www.accv.es, https://example.com, http://example.com, http://other.com/cps, http://example.com/cps, http://myhost.com/myca.crl, http://backup.myhost.com/myca.crl, http://domain.com/some.crl, http://ocsp.domain.com, http://domain.com/ca.crt, http://ca.domain.com, https://xn--80ato2c.cryptography, http://d.om/delta, http://another.local, http://host.com, http://other.com, http://path.to.root/root.crt, http://someregulardomain.com, https://www.xn--80ato2c.cryptography, http://ocsp2.domain.com, http://ocsp3.domain.com, http://ocsp4.domain.com, http://ocsp.other.com, http://ca2.domain.com, http://ca3.domain.com, http://ca4.domain.com, http://ca5.domain.com, https://my.ca.issuer/, http://gv.symcd.com, http://gv.symcb.com/gv.crt, ftp://cryptography.test, http://test.local, http://crypt.og/crl, https://example.org, https://www.example.de, https://www.example.com/, https://www.example.com/0, https://gematik.de/, https://www.kbv.de/ Location: Package overview From: ? → pypi/requests@2.19.1 → pypi/urllib3@2.5.0 → pypi/cryptography@45.0.4 ℹ Read more on: This package | This alert | What are URL strings? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/cryptography@45.0.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		cryptography@45.0.4 has Filesystem access. Location: Package overview From: ? → pypi/requests@2.19.1 → pypi/urllib3@2.5.0 → pypi/cryptography@45.0.4 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/cryptography@45.0.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		cryptography@45.0.4 has URL strings. URLs: https://github.com/pyca/cryptography/, https://datatracker.ietf.org/doc/html/rfc5246#section-7.4.1.4.1 Location: Package overview From: ? → pypi/requests@2.19.1 → pypi/urllib3@2.5.0 → pypi/cryptography@45.0.4 ℹ Read more on: This package | This alert | What are URL strings? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/cryptography@45.0.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		pysocks@1.7.1 has Filesystem access. Location: Package overview From: ? → pypi/requests@2.19.1 → pypi/urllib3@2.5.0 → pypi/pysocks@1.7.1 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pysocks@1.7.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		pysocks@1.7.1 has URL strings. URLs: http://httpbin.org/ip, https://httpbin.org/ip, https://docs.python.org/3/library/socket.html#socket.socket.connect_ex Location: Package overview From: ? → pypi/requests@2.19.1 → pypi/urllib3@2.5.0 → pypi/pysocks@1.7.1 ℹ Read more on: This package | This alert | What are URL strings? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pysocks@1.7.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		pysocks@1.7.1 is Unmaintained. Last Publish: 9/20/2019, 2:06:20 AM From: ? → pypi/requests@2.19.1 → pypi/urllib3@2.5.0 → pypi/pysocks@1.7.1 ℹ Read more on: This package | This alert | What are unmaintained packages? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pysocks@1.7.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		pysocks@1.7.1 has URL strings. URLs: https://github.com/Anorov/PySocks, https://docs.python.org/3/library/socket.html#socket.socket.connect_ex, http://httpbin.org/ip, https://httpbin.org/ip Location: Package overview From: ? → pypi/requests@2.19.1 → pypi/urllib3@2.5.0 → pypi/pysocks@1.7.1 ℹ Read more on: This package | This alert | What are URL strings? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pysocks@1.7.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		urllib3@2.5.0 has Environment variable access. Location: Package overview From: requirements.txt → pypi/urllib3@2.5.0 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/urllib3@2.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		urllib3@2.5.0 has URL strings. URLs: https://opencollective.com/urllib3/updates/urllib3-is-fundraising-for-http-2-support, https://docs.python.org/3, https://github.com/urllib3/urllib3/issues/3020, https://github.com/urllib3/urllib3/issues/2168, https://urllib3.readthedocs.io/en/latest/advanced-usage.html, http://google.com/, https://github.com/WebAssembly/js-promise-integration/blob/main/proposals/js-promise-integration/Overview.md, https://github.com/koenvo/pyodide-http/issues/22, https://www.rfc-editor.org/rfc/rfc8259#section-8.1, https://www.pyopenssl.org, https://cryptography.io, https://github.com/kjd/idna, https://urllib3.readthedocs.io/en/latest/advanced-usage.html#socks-proxies, https://tools.ietf.org/html/rfc2388#section-4.4, https://html.spec.whatwg.org/multipage/, https://github.com/urllib3/urllib3/issues/3290, https://httpwg.org/specs/rfc9113.html#n-field-validity, https://google.com/, https://google.com/mail, https://yahoo.com/, https://github.com/urllib3/urllib3/issues/2920, https://httpbin.org/, https://twitter.com/, https://github.com/urllib3/urllib3/issues/2513#issuecomment-1152559900, https://github.com/urllib3/urllib3/issues/2192#issuecomment-821832963, https://foss.heptapod.net/pypy/pypy/-/issues/3539, http://tools.ietf.org/html/rfc6125#section-6.4.3, https://example.com/, http://hg.python.org/cpython/file/603b4d593758/Lib/socket.py#l535, https://google.com/mail/, http://google.com/mail/, http://example.org, http://16.17.18.19, http://example.com, http://bugs.python.org/issue2550, http://msdn2.microsoft.com/en-us/library/ms740621, http://google.com, http://google.com:80/, http://google.com/abra/cadabra, http://google.com:42/, http://google.com:42/abracadabra, http://google.com/abracadabra, http://google.com:80/abracadabra, https://google.com:443/, https://google.com/abracadabra, https://google.com:443/abracadabra, http://yahoo.com/, http://google.com:42, https://google.net/, https://google.com:42, https://google.com, http://google.com:443, https://google.com:80, https://google.com:443, http://google.com:80, https://google.com/abra/cadabra, http://google.com./, https://google.com./, http://yahoo.com:80, https://github.com/urllib3/urllib3/issues/651, http://www.google.com/mail, https://www.google.com/, https://www.google.com/mail, http://yahoo.com, http://bing.com, http://example.com/, http://example.com:8000/, http://other.example.com/, https://example.com:4333/, https://other.example.com/, HTTPS://EXAMPLE.COM/, HTTP://EXAMPLE.COM/, https://example.com, http://pypi.org/project/urllib3/, http://pypi.org:8080/project/urllib3/, https://anotherurl.com, https://www.example.com, http://www.testing.com/, http://google.com/mail, http://www.google.com, http://mail.google.com, http://google.com:8000/mail/, http://google.com:8000, https://google.com:8000, http://google.com/foo=http://bar:42/baz, http://google.com?foo=http://bar:42/baz, http://google.com#foo=http://bar:42/baz, http://173.194.35.7, http://173.194.35.7/test, http://173.194.35.7:80, http://173.194.35.7:80/test, HTTP://GOOGLE.COM/mail/, HTTP://GoOgLe.CoM:8000/mail/, HTTP://173.194.35.7, http://google.com:foo, http://google.com:-80, http://google.com:65536, HTTP://GOOGLE.COM/MAIL/, http://google.com/MAIL/, HTTPS://Example.Com/?Key=Value, https://example.com/?Key=Value, Https://Example.Com/#Fragment, https://example.com/#Fragment, http://google.com/p, http://google.com/p%5B%5D?parameter%5B%5D=%22hello%22#fragment%23, http://google.com/p%5B%5d?parameter%5b%5D=%22hello%22#fragment%23, http://google.com?foo, http://google.com:/, http://google.com?q=, http://google.com#, https://www.google.com:-80/, https://example.com:0000000000080, https://example.com:0, https://example.com:000000000000, http://google.com:80/mail, http://192.168.0.1/path, http://192.168.0.1:80/path, http://google.com#@evil.com/, http://127.0.0.1%0d%0aConnection%3a%20keep-alive, http://127.0.0.1:6379?, ftp://google.com, http://www.google.com/, https://github.com/urllib3/urllib3/issues/2513 Location: Package overview From: requirements.txt → pypi/urllib3@2.5.0 ℹ Read more on: This package | This alert | What are URL strings? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/urllib3@2.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		urllib3@2.5.0 has URL strings. URLs: https://github.com/urllib3/urllib3/issues/3020, https://github.com/urllib3/urllib3/issues/2168, https://urllib3.readthedocs.io/en/latest/advanced-usage.html, http://google.com/, https://github.com/WebAssembly/js-promise-integration/blob/main/proposals/js-promise-integration/Overview.md, https://github.com/koenvo/pyodide-http/issues/22, https://www.rfc-editor.org/rfc/rfc8259#section-8.1, https://www.pyopenssl.org, https://cryptography.io, https://github.com/kjd/idna, https://urllib3.readthedocs.io/en/latest/advanced-usage.html#socks-proxies, https://tools.ietf.org/html/rfc2388#section-4.4, https://html.spec.whatwg.org/multipage/, https://github.com/urllib3/urllib3/issues/3290, https://httpwg.org/specs/rfc9113.html#n-field-validity, https://google.com/, https://google.com/mail, https://yahoo.com/, https://github.com/urllib3/urllib3/issues/2920, https://httpbin.org/, https://twitter.com/, https://github.com/urllib3/urllib3/issues/2513#issuecomment-1152559900, https://github.com/urllib3/urllib3/issues/2192#issuecomment-821832963, https://foss.heptapod.net/pypy/pypy/-/issues/3539, http://tools.ietf.org/html/rfc6125#section-6.4.3, https://example.com/, http://hg.python.org/cpython/file/603b4d593758/Lib/socket.py#l535, https://google.com/mail/, http://google.com/mail/ Location: Package overview From: requirements.txt → pypi/urllib3@2.5.0 ℹ Read more on: This package | This alert | What are URL strings? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/urllib3@2.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report