Skip to content
Noroxi
CVE-2014-8991· NVD / CVE Program· CNA mitre

pip 1.3 through 1.5.6 allows local users to cause a denial of service (prevention of package installation) by creating a /tmp/pip-build-* fi

pip 1.3 through 1.5.6 allows local users to cause a denial of service (prevention of package installation) by creating a /tmp/pip-build-* file for another user.

LowCVSS 2.1 · v2.0—No exploit Fix available
Published
Nov 24, 2014
Updated
Jun 16, 2026
EPSS
0.4% · 31th percentile
CWE
—
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

8

Monitor

Low priority for now.

CVSS
8 / 40 · 2.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

Affected systems

VendorProduct
pypapip
oraclesolaris

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • oracle solaris11.2
  • pypa pip1.3 and later · up to 1.5.6 inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12python-pipbefore 1.5.6-41.5.6-4
openSUSE:Tumbleweedpython-pipbefore 9.0.1-1.19.0.1-1.1
openSUSE:Tumbleweedpython2-pipbefore 20.0.2-2.620.0.2-2.6
PyPIpipfrom 1.3 · before 6.06.0
SUSE:Linux Enterprise Module for Basesystem 15 SP3python39-pipbefore 20.2.4-7.5.120.2.4-7.5.1
SUSE:Linux Enterprise Module for Basesystem 15 SP3python39-setuptoolsbefore 44.1.1-7.3.144.1.1-7.3.1
SUSE:Linux Enterprise Module for Public Cloud 12python-jmespathbefore 0.9.2-10.6.10.9.2-10.6.1
SUSE:Linux Enterprise Module for Public Cloud 12python-jsonschemabefore 2.2.0-3.3.12.2.0-3.3.1
SUSE:Linux Enterprise Module for Public Cloud 12python-paramikobefore 1.18.5-2.15.11.18.5-2.15.1
SUSE:OpenStack Cloud 7python-pipbefore 10.0.1-11.6.110.0.1-11.6.1
SUSE:OpenStack Cloud 7python-plybefore 3.4-3.3.13.4-3.3.1

Same product

pypa: all records

Other highest-scoring records for the same primary product.

  • CVE-2018-20225An issue was discovered in pip (all versions) because it installs the version with the highest version number, even if the user had intended
    32Monitor
  • CVE-2019-20916The pip package before 19.2 for Python allows Directory Traversal when a URL is given in an install command, because a Content-Disposition h
    31Monitor
  • CVE-2013-1629pip before 1.3 uses HTTP to retrieve packages from the PyPI repository, and does not perform integrity checks on package contents, which all
    29Monitor
  • CVE-2013-5123The mirroring support (-M, --use-mirrors) in Python Pip before 1.5 uses insecure DNS querying and authenticity checks which allows attackers
    25Monitor
  • CVE-2021-3572A flaw was found in python-pip in the way it handled Unicode separators in git references.
    23Monitor
  • CVE-2026-13346pip absolute path traversal during download from malicious package indexes
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:python-pip1.5.6-4 · Debian:12Package registry (OSV)
opensuse:python-pip9.0.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python2-pip20.0.2-2.6 · openSUSE:TumbleweedPackage registry (OSV)
PyPI:pip6.0Package registry (OSV)
suse:python-jmespath0.9.2-10.6.1 · SUSE:Linux Enterprise Module for Public Cloud 12Package registry (OSV)
suse:python-jsonschema2.2.0-3.3.1 · SUSE:Linux Enterprise Module for Public Cloud 12Package registry (OSV)
suse:python-paramiko1.18.5-2.15.1 · SUSE:Linux Enterprise Module for Public Cloud 12Package registry (OSV)
suse:python-pip10.0.1-11.6.1 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:python-ply3.4-3.3.1 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:python39-pip20.2.4-7.5.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP3Package registry (OSV)
suse:python39-setuptools44.1.1-7.3.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
P · the service can be disrupted
Attack complexity
Low
Confidentiality impact
None
Integrity impact
None
Availability impact
P

Weakness class (CWE)

—

CVSS vector

AV:L/AC:L/Au:N/C:N/I:N/A:P

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records