Skip to content

[Snyk] Security upgrade urllib3 from 1.25.11 to 2.5.0 - #925

Closed
jecos wants to merge 1 commit into
masterfrom
snyk-fix-708f8389e6f2e17efe859cb747ad9762
Closed

[Snyk] Security upgrade urllib3 from 1.25.11 to 2.5.0#925
jecos wants to merge 1 commit into
masterfrom
snyk-fix-708f8389e6f2e17efe859cb747ad9762

Conversation

@jecos

@jecos jecos commented Jul 15, 2025

Copy link
Copy Markdown
Member

snyk-top-banner

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.22.0 has requirement urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1, but you have urllib3 1.26.20.
graphene-django 3.2.3 has requirement Django>=3.2, but you have Django 2.2.26.
graphene-django 3.2.3 has requirement graphql-relay<4,>=3.1.1, but you have graphql-relay 2.0.1.
graphene-django 3.2.3 has requirement graphene<4,>=3.0, but you have graphene 2.1.8.
graphene-django 3.2.3 has requirement graphql-core<4,>=3.1.0, but you have graphql-core 2.3.2.
django-redis-cache 3.0.0 has requirement redis<4.0, but you have redis 5.0.8.

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

@znatty22 znatty22 closed this Oct 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants