Update dependency pip to v25 [SECURITY] #150
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
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pypi-pip-vulnerability
branch
from
2c692c2 to
411e56a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
==23.1.2->==25.3GitHub Vulnerability Alerts
CVE-2023-5752
When installing a package from a Mercurial VCS URL, e.g.
pip install hg+..., with pip prior to v23.3, the specified Mercurial revision could be used to inject arbitrary configuration options to thehg clonecall (e.g.--config). Controlling the Mercurial configuration can modify how and which repository is installed. This vulnerability does not affect users who aren't installing from Mercurial.CVE-2025-8869
Summary
In the fallback extraction path for source distributions,
pipused Python’starfilemodule without verifying that symbolic/hard link targets resolve inside the intended extraction directory. A malicious sdist can include links that escape the target directory and overwrite arbitrary files on the invoking host duringpip install.Impact
Successful exploitation enables arbitrary file overwrite outside the build/extraction directory on the machine running
pip. This can be leveraged to tamper with configuration or startup files and may lead to further code execution depending on the environment, but the direct, guaranteed impact is integrity compromise on the vulnerable system.Conditions
The issue is triggered when installing an attacker-controlled sdist (e.g., from an index or URL) and the fallback extraction code path is used. No special privileges are required beyond running
pip install; active user action is necessary.Remediation
The fix is available starting in pip
25.3. Using a Python interpreter that implements the safe-extraction behavior described by PEP 706 provides additional defense in depth for othertarfileissues but is not a substitute for upgrading pip for this specific flaw.Release Notes
pypa/pip (pip)
v25.3Compare Source
v25.2Compare Source
v25.1.1Compare Source
v25.1Compare Source
v25.0.1Compare Source
v25.0Compare Source
v24.3.1Compare Source
v24.3Compare Source
v24.2Compare Source
v24.1.2Compare Source
v24.1.1Compare Source
v24.1Compare Source
v24.0Compare Source
v23.3.2Compare Source
v23.3.1Compare Source
v23.3Compare Source
v23.2.1Compare Source
v23.2Compare Source
Configuration
📅 Schedule: Branch creation - "" in timezone Europe/London, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.