Approved changes feed: RSS · Atom
cpe:2.3:a:python_software_foundation:pymanager:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Python Software Foundation (461e81ff-7c75-5ab8-b66d-98945db219c0) |
|---|---|
| Product | Pymanager (9808e50f-f1b5-5c8d-a1ac-32904971232e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-5271 |
vulnerable | 2026-06-08 08:07:03.466879 |
Possible to hijack modules in current working directory
pymanager included the current working directory in sys.path meaning modules could be shadowed by modules in the current working directory. As a result, if a user executes a pymanager-generated command (e.g., pip, pytest)
from an attacker-controlled directory, a malicious module in that
directory can be imported and executed instead of the intended package.
Published: 2026-04-01T13:48:07.534Z
Updated: 2026-04-01T23:12:18.741Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.