CVE-2026-47763pdm: Project-Local State and Config Writes Follow Symlinks

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.

Affected packages & fixed versions

Affected products (as reported)

References

• https://github.com/pdm-project/pdm/security/advisories/GHSA-ghq2-5c67-fprm x_refsource_CONFIRM
• https://github.com/pdm-project/pdm/releases/tag/2.27.0 x_refsource_MISC