CVE-2013-1629: Improper Input Validation in pip

pip Updated 02 Oct 2025

Summary

13/05/2022
Yes i
High
8.4

CVE-2013-1629: Improper Input Validation in pip. Affects pip versions < 1.3. Fixed in 1.3. How to fix ↓

Also tracked for

The same CVE-2013-1629 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

pip is a package management system used to install and manage software packages written in Python. It is the standard package manager for the Python programming language. Pip allows users to easily install, upgrade, and remove Python packages from the PyPI repository. However, prior to version 1.3, pip used HTTP to retrieve packages from PyPI and did not perform integrity checks on package contents.

Vulnerability Detail

The vulnerability (CVE-2013-1629) in pip arises from the lack of proper input validation during the 'pip install' operation. This allows man-in-the-middle attackers to execute arbitrary code by crafting a malicious response to the installation request. As pip did not perform integrity checks on package contents, an attacker could tamper with the package during transit and inject malicious code. This vulnerability poses a moderate risk as it can lead to the execution of arbitrary code on the target system.

How To Fix

Latest published version: 26.2.2 as of 22 Oct 2026

pip install --upgrade "pip==26.2.2"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.3

This is the first release that contains the fix.

pip install --upgrade "pip==1.3"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. However, users can mitigate the risk by ensuring they are using an updated version of pip (1.3 or later) that performs integrity checks on package contents.

Conclusion

In conclusion, the vulnerability (CVE-2013-1629) in pip allows man-in-the-middle attackers to execute arbitrary code by tampering with package contents during transit. To mitigate this risk, it is recommended to upgrade to pip version 1.3 or later, which performs integrity checks on package contents. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for pip →

Share this vulnerability

FAQ

Pip is a package management system for Python that allows users to easily install, upgrade, and remove Python packages from the PyPI repository.

The vulnerability allows man-in-the-middle attackers to execute arbitrary code on the target system by tampering with package contents during transit.

To fix this vulnerability, upgrade to pip version 1.3 or later by running 'pip install --upgrade pip'.

While there is no specific workaround mentioned, users can mitigate the risk by using an updated version of pip that performs integrity checks on package contents.

The severity of this vulnerability is rated as MODERATE.

Related vulnerabilities

Recent vulnerabilities recorded for pip.

How To Fix

Latest published version: 26.2.2 as of 22 Oct 2026

pip install --upgrade "pip==26.2.2"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.3

This is the first release that contains the fix.

pip install --upgrade "pip==1.3"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback