Code execution via post-install self-check imports
Published Apr 27, 2026 · Updated Apr 27, 2026
Untrusted module loading in Python Packaging Authority pip before 26.1 allows attackers to execute code via a malicious wheel. The install command completed wheel installation before its deferred self-version check imported network-stack modules, allowing same-named files from the newly installed wheel to enter the process. A user must actively install the crafted wheel with sufficient privileges; successful exploitation can read or modify data accessible to that pip process.
Summary
What happened
Untrusted module loading in Python Packaging Authority pip before 26.1 allows attackers to execute code via a malicious wheel. The install command completed wheel installation before its deferred self-version check imported network-stack modules, allowing same-named files from the newly installed wheel to enter the process. A user must actively install the crafted wheel with sufficient privileges; successful exploitation can read or modify data accessible to that pip process.
The record
- CVE
- CVE-2026-6357
- Published
- Apr 27, 2026
- Updated
- Apr 27, 2026
- Vendor
- Python Packaging Authority
- Product
- pip
- Classifications
- CWE-829, T1204.002
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 27, 2026CVE publishedPublication date reported by the CVE source.
- Apr 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <26.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo