security: upgrade urllib3 to 1.26.20#7730
Open
wtfiwtz wants to merge 2 commits into
Open
Conversation
Upgrade urllib3 to 1.26.20 to fix security vulnerabilities: - urllib3: 1.26.19 → 1.26.20 Security fixes: - CVE-2025-50181: Redirect vulnerability - CVE-2025-50182: SSRF-class vulnerability This is the 1.26.x patch release. The migration to urllib3 2.x with the champion SSRF protection library is tracked separately in PR getredash#7721. Related: split from orchestrated-io/redash#7719 Co-authored-by: Cursor <cursoragent@cursor.com>
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Description
Upgrade urllib3 to 1.26.20 to fix security vulnerabilities:
Security fixes:
This is the 1.26.x patch release. The migration to urllib3 2.x with the champion SSRF protection library is tracked separately in PR #7721.
How is this tested?
Related Tickets & Documents
Split from orchestrated-io/redash#7719 per @zachliu's review feedback to separate independent dependency upgrades.
Part of the security vulnerability remediation work tracked in #7711.
Note
This PR is marked as draft until manual testing is complete.
Made with Cursor