Bump citusdata/mitmproxy fork to close pyOpenSSL CVE alerts#8596
Open
ihalatci wants to merge 2 commits into
Open
Bump citusdata/mitmproxy fork to close pyOpenSSL CVE alerts#8596ihalatci wants to merge 2 commits into
ihalatci wants to merge 2 commits into
Conversation
Updates the mitmproxy git ref in both Pipfiles from the pinned commit SHA (70bad9a3c098...) to track our fork's main branch. After citusdata/mitmproxy#4 (merge of upstream main), the fork now caps pyOpenSSL at <=27.0.0 (was <=25.3.0), unblocking lockfile resolution past pyOpenSSL 25.3.0. Re-locking both Pipfiles resolves pyopenssl to 26.2.0, closing all four open Dependabot security alerts: #126 / #125 CVE-2026-27459 (HIGH) patched >=26.0.0 #124 / #123 CVE-2026-27448 (low) patched >=26.0.0 Other deps that naturally moved up within existing constraint ranges during re-lock (no Pipfile-level pin changes): asgiref 3.11.0 -> 3.11.1 certifi 2026.2.25 -> 2026.5.20 click 8.3.2 -> 8.4.1 filelock 3.28.0 -> 3.29.0 packaging 26.1 -> 26.2 psycopg 3.3.3 -> 3.3.4 pytest-asyncio 1.3.0 -> 1.4.0 urwid 3.0.5 -> 4.0.0 wcwidth 0.6.0 -> 0.7.0 The .devcontainer/src/test/regress Pipfile.lock is kept byte- identical to src/test/regress/Pipfile.lock per the convention established in #8488 and #8547. DESCRIPTION: Update mitmproxy fork to lift pyOpenSSL cap; re-lock to 26.2.0 (closes CVE-2026-27459, CVE-2026-27448) Closes #123 Closes #124 Closes #125 Closes #126 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8596 +/- ##
==========================================
- Coverage 88.76% 88.75% -0.01%
==========================================
Files 288 288
Lines 64302 64303 +1
Branches 8091 8092 +1
==========================================
Hits 57075 57075
- Misses 4888 4889 +1
Partials 2339 2339 🚀 New features to boost your workflow:
|
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.
DESCRIPTION: Update mitmproxy fork to lift pyOpenSSL cap; re-lock to 26.2.0 (closes CVE-2026-27459, CVE-2026-27448)
Summary
Bumps the
mitmproxygit ref in both Pipfiles from the pinned commit SHA70bad9a3c098...to trackcitusdata/mitmproxy@main. After citusdata/mitmproxy#4 (merge of upstreammitmproxy/mitmproxy@main), our fork'smaincapspyOpenSSL<=27.0.0(was<=25.3.0), unblocking the lockfile from resolving past pyOpenSSL 25.3.0.Re-locking both Pipfiles via
pipenv lockresolvespyopensslto 26.2.0, closing all four currently-open Dependabot security alerts:>=26.0.0>=26.0.0Pipfile changes
Single line per file, in both:
src/test/regress/Pipfile.devcontainer/src/test/regress/PipfileThe
ref="main"form is supported by pipenv for git deps; the resolved commit SHA (df5879516a57ea780e1cc88edaf2051e1d32915f— the merge commit of mitmproxy#4) is pinned inPipfile.lock, preserving reproducibility.Lockfile-level changes (re-lock side-effects, no Pipfile pin changes)
70bad9a3...(==12.2.2)df5879516a...(==13.0.0.dev0)main==25.3.0==26.2.0==3.11.0==3.11.1==2026.2.25==2026.5.20==8.3.2==8.4.1==3.28.0==3.29.0==26.1==26.2==3.3.3==3.3.4==1.3.0==1.4.0==3.0.5==4.0.0==0.6.0==0.7.0Per scope direction, no other direct deps were bumped — only the security-driven
mitmproxyref change. Other transitive movements above are natural consequences ofpipenv lock --clearagainst unchanged version constraints.Validation
Both
src/test/regress/Pipfile.lockand.devcontainer/src/test/regress/Pipfile.lockare byte-identical, per the convention established in #8488 and #8547.Notes
pipenv lock --clear(pipenv 2025.0.3, Python 3.12.12).citusdata/the-processwill regenerate the threecircleci/images/*/files/etc/requirements.txtfiles (which are generated from thisPipfile.lockviapipenv requirements) once this lands.Closes #123
Closes #124
Closes #125
Closes #126