Update gitpython version - #70265
Open
dwoz wants to merge 1 commit into
Open
Conversation
…for CVE-2026-78676 Six ``requirements/static/ci/py3.*/lint.lock`` files still pinned ``gitpython==3.1.50``, which is in the vulnerable range for CVE-2026-78676 (GHSA-284h-m62q-gf8w): GitPython re-serialization corrupts a dormant multi-line quoted config value into an executable directive (e.g. ``core.hooksPath``), enabling RCE via crafted config files. Lint environments installed from these locks, so this was a live (though limited-blast-radius) exposure. The runtime lock files (``{cloud,darwin,docs,freebsd,linux,windows}.lock``) and the base pin were already at ``>=3.1.60`` / ``==3.1.60`` and unaffected. Bump the six lint locks to ``==3.1.60`` to match the rest of the lock chain. Also align the two CI-static lower bounds ``requirements/static/ci/{common,darwin}.txt`` from ``>=3.1.50`` to ``>=3.1.59`` so any subsequent pip-compile can't drift a lock back into the vulnerable range.
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
2 participants
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.
CVE-2026-78676
Six
requirements/static/ci/py3.*/lint.lockfiles still pinnedgitpython==3.1.50, which is in the vulnerable range for CVE-2026-78676 (GHSA-284h-m62q-gf8w): GitPython re-serialization corrupts a dormant multi-line quoted config value into an executable directive (e.g.core.hooksPath), enabling RCE via crafted config files. Lint environments installed from these locks, so this was a live (though limited-blast-radius) exposure. The runtime lock files ({cloud,darwin,docs,freebsd,linux,windows}.lock) and the base pin were already at>=3.1.60/==3.1.60and unaffected.Bump the six lint locks to
==3.1.60to match the rest of the lock chain. Also align the two CI-static lower boundsrequirements/static/ci/{common,darwin}.txtfrom>=3.1.50to>=3.1.59so any subsequent pip-compile can't drift a lock back into the vulnerable range.