chore(deps): update dependency pip to v26 [security]

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
pip (changelog)	==25.0.1 → ==26.0

---

pip's fallback tar extraction doesn't check symbolic links point to extraction directory

CVE-2025-8869 / GHSA-4xh5-x5gv-qwph

More information

Details

When extracting a tar archive pip may not check symbolic links point into the extraction directory if the tarfile module doesn't implement PEP 706. Note that upgrading pip to a "fixed" version for this vulnerability doesn't fix all known vulnerabilities that are remediated by using a Python version that implements PEP 706. Note that this is a vulnerability in pip's fallback implementation of tar extraction for Python versions that don't implement PEP 706 and therefore are not secure to all vulnerabilities in the Python 'tarfile' module. If you're using a Python version that implements PEP 706 then pip doesn't use the "vulnerable" fallback code. Mitigations include upgrading to a version of pip that includes the fix, upgrading to a Python version that implements PEP 706 (Python >=3.9.17, >=3.10.12, >=3.11.4, or >=3.12), applying the linked patch, or inspecting source distributions (sdists) before installation as is already a best-practice.

Severity

• CVSS Score: 5.9 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

References

• https://nvd.nist.gov/vuln/detail/CVE-2025-8869
• https://github.com/pypa/pip/pull/13550
• https://mail.python.org/archives/list/security-announce@python.org/thread/IF5A3GCJY3VH7BVHJKOWOJFKTW7VFQEN
• https://github.com/pypa/pip/commit/f2b92314da012b9fffa36b3f3e67748a37ef464a
• https://pip.pypa.io/en/stable/news/#v25-2
• https://lists.debian.org/debian-lts-announce/2025/10/msg00028.html
• https://github.com/advisories/GHSA-4xh5-x5gv-qwph

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

pip Path Traversal vulnerability

CVE-2026-1703 / GHSA-6vgw-5pg2-w6jp

More information

Details

When pip is installing and extracting a maliciously crafted wheel archive, files may be extracted outside the installation directory. The path traversal is limited to prefixes of the installation directory, thus isn't able to inject or overwrite executable files in typical situations.

Severity

• CVSS Score: 2.0 / 10 (Low)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

References

• https://nvd.nist.gov/vuln/detail/CVE-2026-1703
• https://github.com/pypa/pip/pull/13777
• https://github.com/pypa/pip/commit/8e227a9be4faa9594e05d02ca05a413a2a4e7735
• https://mail.python.org/archives/list/security-announce@python.org/thread/WIEA34D4TABF2UNQJAOMXKCICSPBE2DJ
• https://github.com/advisories/GHSA-6vgw-5pg2-w6jp

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

pypa/pip (pip)

v26.0

Compare Source

v25.3

Compare Source

v25.2

Compare Source

v25.1.1

Compare Source

v25.1

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • ""
• 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[gemini-code-assist]

Code Review

This pull request updates the pip version to 25.3 in the requirements.txt file for the google-crc32c package. The reviewer noted that since pip is a shared tool, this update should ideally be applied consistently across all packages in the repository rather than being handled piecemeal in individual pull requests.

[gemini-code-assist]

This update to pip is being applied to a single package's requirements file. According to the general rules for this repository, changes to shared configurations or tooling should be applied consistently across all relevant packages in a dedicated, universal change rather than piecemeal in individual pull requests. Since pip is a shared tool used across the repository, consider applying this security update globally to ensure consistency and security across all packages.

References

1. Changes to shared configurations, like mypy flags, should be applied consistently across all relevant packages in a dedicated, universal change rather than piecemeal in individual pull requests.