The mirroring support (-M, --use-mirrors) in Python Pip before 1.5 uses insecure DNS querying and authenticity checks which allows attackers
Noroxi assessment
Priority: Monitor (action score 25/100)
- Public proof-of-concept code exists (Exploit-DB); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 7.9% (FIRST EPSS); higher than 94.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: python-pip (Debian:12) 1.4.1-1; python-pip (openSUSE:Tumbleweed) 9.0.1-1.1; python2-pip (openSUSE:Tumbleweed) 20.0.2-2.6.
Low priority for now. Upgrade to python-pip (Debian:12) 1.4.1-1; python-pip (openSUSE:Tumbleweed) 9.0.1-1.1; python2-pip (openSUSE:Tumbleweed) 20.0.2-2.6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
The mirroring support (-M, --use-mirrors) in Python Pip before 1.5 uses insecure DNS querying and authenticity checks which allows attackers to perform man-in-the-middle attacks.
- Published
- Nov 5, 2019
- Updated
- Jun 16, 2026
- EPSS
- 8.0% · 95th percentile
- CWE
- CWE-287
Report tools
Action score
25
Monitor
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 8.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| pypa | pip | cpe:2.3:a:pypa:pip |
| virtualenv | virtualenv | cpe:2.3:a:virtualenv:virtualenv |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| redhat | openshift | cpe:2.3:a:redhat:openshift |
| redhat | software collections | cpe:2.3:a:redhat:software_collections |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- debian debian linux8.0
- debian debian linux9.0
- fedoraproject fedora20
- fedoraproject fedora21
- pypa pipbefore 1.5
- redhat openshift1.0
- redhat openshift2.0
- redhat software collectionsall versions
- virtualenv virtualenv12.0.7
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | python-pip | before 1.4.1-1 | 1.4.1-1 |
| openSUSE:Tumbleweed | python-pip | before 9.0.1-1.1 | 9.0.1-1.1 |
| openSUSE:Tumbleweed | python2-pip | before 20.0.2-2.6 | 20.0.2-2.6 |
| PyPI | pip | before 1.5 | 1.5 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP3 | python39-pip | before 20.2.4-7.5.1 | 20.2.4-7.5.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP3 | python39-setuptools | before 44.1.1-7.3.1 | 44.1.1-7.3.1 |
| SUSE:Linux Enterprise Module for Public Cloud 12 | python-jmespath | before 0.9.2-10.6.1 | 0.9.2-10.6.1 |
| SUSE:Linux Enterprise Module for Public Cloud 12 | python-jsonschema | before 2.2.0-3.3.1 | 2.2.0-3.3.1 |
| SUSE:Linux Enterprise Module for Public Cloud 12 | python-paramiko | before 1.18.5-2.15.1 | 1.18.5-2.15.1 |
| SUSE:OpenStack Cloud 7 | python-pip | before 10.0.1-11.6.1 | 10.0.1-11.6.1 |
| SUSE:OpenStack Cloud 7 | python-ply | before 3.4-3.3.1 | 3.4-3.3.1 |
Same product
pypa: all recordsOther 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 intended32Monitor
- 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 h31Monitor
- 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 all29Monitor
- 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 indexes22Monitor
- CVE-2026-8643pip can extract console_scripts and gui_scripts outside installation directory16Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:python-pip | 1.4.1-1 · Debian:12 | Package registry (OSV) |
| opensuse:python-pip | 9.0.1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:python2-pip | 20.0.2-2.6 · openSUSE:Tumbleweed | Package registry (OSV) |
| PyPI:pip | 1.5 | Package registry (OSV) |
| suse:python-jmespath | 0.9.2-10.6.1 · SUSE:Linux Enterprise Module for Public Cloud 12 | Package registry (OSV) |
| suse:python-jsonschema | 2.2.0-3.3.1 · SUSE:Linux Enterprise Module for Public Cloud 12 | Package registry (OSV) |
| suse:python-paramiko | 1.18.5-2.15.1 · SUSE:Linux Enterprise Module for Public Cloud 12 | Package registry (OSV) |
| suse:python-pip | 10.0.1-11.6.1 · SUSE:OpenStack Cloud 7 | Package registry (OSV) |
| suse:python-ply | 3.4-3.3.1 · SUSE:OpenStack Cloud 7 | Package registry (OSV) |
| suse:python39-pip | 20.2.4-7.5.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP3 | Package registry (OSV) |
| suse:python39-setuptools | 44.1.1-7.3.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP3 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | webapps | 2013-01-13 |
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.
- First PoC-2488 d
- Published
- TodayOct 13, 2026+2534 d
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.
No commit or PR link among the references.
Credits
All researchersFinders, 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
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middlewareapp.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- lists.fedoraproject.org/pipermail/package-announce/2015-April/155291.html
- www.openwall.com/lists/oss-security/2013/08/21/17
- www.openwall.com/lists/oss-security/2013/08/21/18
- www.securityfocus.com/bid/77520
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-5123
- bugzilla.suse.com/show_bug.cgi?id=CVE-2013-5123
- security-tracker.debian.org/tracker/CVE-2013-5123
Vendor advisories and official records. Exploit/PoC links are deliberately left out.