pdm is a Python package and dependency manager supporting the latest PEP standards. Versions prior to 2.27.0 are vulnerable to path traversal through write_to_fs. InstallDestination.write_to_fs() in src/pdm/installers/installers.py overrides the base class to add symlink/hardlink support but replaces the safe _path_with_destdir() (which validates via Path.resolve() + is_relative_to()) with a bare os.path.join() that performs no path validation. A malicious wheel with traversal entries can write arbitrary files. This issue has been fixed in version 2.27.0.
CVE-2026-47764
This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.4
- EG Score
- 8.4(medium)
- EG Risk
- 53(Track)EG Risk 53/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity84% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 4%
- KEV
- Not listed
Published
June 10, 2026
Last Modified
August 5, 2026
Advisory Details (2)
Auto-updated Aug 4, 2026v2.27.0
Patch available: pdm-project/pdm 2.27.0
https://github.com/pdm-project/pdm/releases/tag/2.27.0Path traversal in wheel installation via overridden write_to_fs (CWE-22) · Advisory · pdm-project/pdm · GitHub
https://github.com/pdm-project/pdm/security/advisories/GHSA-78v8-vpjp-cjqhVendor Advisories for CVE-2026-47764(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(4 across 4 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| pdm | 2.2.1+ds1-1 ... 2.28.0-1 (14 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| pdm | 2.20.1+ds1-2 ... 2.28.0-1 (9 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| pdm | 2.20.1+ds1-2 ... 2.26.6-1 (7 versions) | 2.27.0-1 | — |
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| pdm | 0.0.0 ... 2.9.3 (247 versions) | 2.27.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 41× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 00:19 UTCEG score recompute
- 2026-08-23 10:46 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 08:00 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 08:52 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 14:56 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 23:32 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 11:23 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 10:50 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-13 22:16 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 20:05 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 21:07 UTCEG score recompute
- 2026-08-11 09:39 UTCEG score recompute
Show 22 moreShow fewer
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 23:08 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 00:03 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 01:05 UTCEG score recompute
- 2026-08-06 14:38 UTCEG score recompute
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 03:00 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 15:31 UTCEG score recompute
- 2026-08-05 14:38 UTCEG score recompute
- 2026-08-04 19:26 UTCEG score recompute
- 2026-08-04 18:21 UTCEG score recompute▲ 8.40
- 2026-08-04 18:20 UTCMITRE cvelistV5CVSS v3 → 8.4 · CVSS v4 → 8.4
- 2026-07-30 09:45 UTCEG score recompute
- 2026-07-26 20:56 UTCEG score recompute
- 2026-07-23 03:17 UTCEG score recompute
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-10 21:17 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-47764?
When was CVE-2026-47764 disclosed?
Is CVE-2026-47764 actively exploited?
What is the CVSS score of CVE-2026-47764?
How do I remediate CVE-2026-47764?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47764
Is Your Infrastructure Affected by CVE-2026-47764?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.