Fix possible fix(deps): mitmproxy 11.0.2 → 11.1.2 (CVE-2025-23217) in requirements.txt - #2
Open
begininvoke wants to merge 1 commit into
Open
Conversation
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.
Proposing a fix for something flagged in
backend/requirements.txt. It is around line 63.The project pins mitmproxy version 11.0.2, which is vulnerable to CVE-2025-23217. This flaw allows a remote attacker to reach mitmweb’s internal API via the public proxy listener, enabling SSRF and potentially remote code execution. Because the vulnerable component is exposed on the network, the risk is high. Upgrading to a non‑vulnerable version (≥ 11.1.2) eliminates the issue.
Upgrade mitmproxy from 11.0.2 to 11.1.2 to address CVE‑2025‑23217 while preserving the existing httpcore and bcrypt pins.
For reference: rule
CVE-2025-23217. Rated high.I do not know the codebase, so please check the change fits how the rest of it works. Happy to adjust it or close this if the reasoning is off.
Found with automated scanning (RedGem) and reviewed before opening. If it is not useful, closing it is completely fine.