Skip to content

Sync Citus image requirements to close pyOpenSSL CVE alerts#219

Open
ihalatci wants to merge 1 commit into
masterfrom
sync-citus-image-requirements-pyopenssl-cve
Open

Sync Citus image requirements to close pyOpenSSL CVE alerts#219
ihalatci wants to merge 1 commit into
masterfrom
sync-citus-image-requirements-pyopenssl-cve

Conversation

@ihalatci
Copy link
Copy Markdown
Contributor

Summary

Regenerates the four Citus image requirement files from the updated
Citus Pipfile.lock produced by citusdata/citus#8596,
which lifts the citusdata/mitmproxy
fork's pyOpenSSL cap and pulls pyOpenSSL forward past two CVEs.

Pairs with:

What changed

Three tester images, regenerated via pipenv requirements > requirements.txt
(byte-identical across pgupgradetester, failtester, citusupgradetester):

package before after
pyopenssl 25.3.0 26.2.0
mitmproxy (fork ref) 70bad9a3 df5879516
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

Stylechecker image, regenerated via pipenv requirements --dev-only > requirements.txt
(natural transitive drift from re-locking; no top-level dev deps changed):

package before after
click 8.3.2 8.4.1
packaging 26.1 26.2
pathspec 1.0.4 1.1.1
platformdirs 4.9.6 4.10.0

No new top-level packages added or removed; no dropped pins.

Notes

Same workflow as #214: regenerated artifacts following the instructions
in the file headers rather than hand-edited. Header PR reference bumped
#8547#8596 to track the source lockfile.

Verification

  • Installed both regenerated requirement sets in clean Python 3.12 venvs
    with pip install -r ...; both completed without resolver errors.
  • pip check reports no broken requirements for both sets.
  • Verified the installed pyOpenSSL version is 26.2.0 (closes CVE-2026-27459
    HIGH and CVE-2026-27448) and the installed mitmproxy resolves to the
    post-merge fork ref df5879516.

Regenerates the four image requirements files from Citus's regenerated
Pipfile.lock on citusdata/citus#8596, which lifts the mitmproxy fork's
pyOpenSSL cap and pulls pyOpenSSL forward to a non-vulnerable release.

Tester images (pgupgradetester, failtester, citusupgradetester),
regenerated via 'pipenv requirements > requirements.txt':
  pyopenssl                 25.3.0   -> 26.2.0
  mitmproxy (fork ref)      70bad9a3 -> df5879516
  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

Stylechecker, regenerated via 'pipenv requirements --dev-only':
  click                     8.3.2    -> 8.4.1
  packaging                 26.1     -> 26.2
  pathspec                  1.0.4    -> 1.1.1
  platformdirs              4.9.6    -> 4.10.0

These mirror the natural transitive movements from re-locking the
Citus Pipfile after the mitmproxy ref switched to track main. No new
top-level packages added or removed; no dropped pins.

Verified: clean Python 3.12 venv installs each set without errors and
'pip check' reports no broken requirements.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.

1 participant