CVE-2026-47763 pdm: Project-Local State and Config Writes Follow Symlinks
Attackers can overwrite arbitrary files via symlinked config files in malicious repositories, leading to data modification.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-47763?
CVE-2026-47763 is a medium-severity path traversal vulnerability in pdm-project pdm, published on 4 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
pdm is a Python package and dependency manager supporting the latest PEP standards. In versions prior to 2.27.0, pdm writes several project-local state or configuration files without symlink protection. If a malicious repository places those files as symlinks, local PDM operations can overwrite the symlink targets. This creates an arbitrary file clobber primitive relative to the privileges of the invoking user. Config.__init__() resolves the project-local pdm.toml path and _save_config() writes to the resolved target. If PROJECT_ROOT/pdm.toml is a symlink to another file, pdm config -l ... updates the target file instead of refusing the write. The same general problem exists for other project-local persistence paths that are written directly with no lstat / O_NOFOLLOW protection. For the pdm.toml PoC specifically, the target file must already contain parseable TOML. Otherwise the load step fails before the write path is reached. That parser constraint does not apply to the .pdm-python or .python-version sinks. This issue has been fixed in version 2.27.0.
Weakness: CWE-61
Which versions are affected by CVE-2026-47763?
3 open source packages ship an affected version, including pdm.
| Package | Affected | Fixed in |
|---|---|---|
pdm PyPI | All versions | 2.27.0 |
pdm PyPI | All versions | 2.27.0 |
pdm PyPI | All versions | 2.27.0 |
How do I fix CVE-2026-47763?
Upgrade pdm to 2.27.0 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-47763 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47763 exists.
Sources
Also known as DEBIAN-CVE-2026-47763, GHSA-ghq2-5c67-fprm, PYSEC-2026-2862, UBUNTU-CVE-2026-47763.