Is CVE-2026-47763 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-47763 being exploited in the wild.

How severe is CVE-2026-47763?

Medium severity, with a CVSS score of 4, published 4 August 2026.

Which products and versions are affected?

pdm (PyPI) < 2.27.0, ECOSYSTEM:introduced=0,fixed=2.27.0.

Is there a fix for CVE-2026-47763?

Yes. pdm (PyPI): upgrade to 2.27.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-47763 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-47763?

Check whether you run pdm (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47763: pdm-project PDM symlink following in project-local config writes

Q: Which products and versions are affected?

pdm (PyPI) < 2.27.0, ECOSYSTEM:introduced=0,fixed=2.27.0.

Q: Is there a fix for CVE-2026-47763?

Yes. pdm (PyPI): upgrade to 2.27.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-47763 attacked?

It is attacked with local access, in a software library.

Q: Am I affected by CVE-2026-47763?

Check whether you run pdm (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47763 · Severity: medium · CVSS 4 · Published 2026-08-04

PDM is a Python package and dependency manager used by developers to manage project environments. A vulnerability exists where PDM fails to check if its local configuration files are symbolic links before writing to them. If a user runs PDM commands within a malicious repository, an attacker could cause PDM to overwrite sensitive files elsewhere on the user's system, potentially leading to data loss or system instability.

Technologies: pdm (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-47763 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47763 being exploited in the wild.
How severe is CVE-2026-47763?: Medium severity, with a CVSS score of 4, published 4 August 2026.
Which products and versions are affected?: pdm (PyPI) < 2.27.0, ECOSYSTEM:introduced=0,fixed=2.27.0.
Is there a fix for CVE-2026-47763?: Yes. pdm (PyPI): upgrade to 2.27.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-47763 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-47763?: Check whether you run pdm (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

pdm (PyPI): upgrade to 2.27.0 or later
```
pip install "pdm>=2.27.0"
```

Technical details

A symlink following vulnerability exists in PDM's project-local configuration handling. The `Config.__init__()` and `_save_config()` methods in `src/pdm/project/config.py` (and related sinks in `core.py` and `use.py`) resolve paths for files like `pdm.toml`, `.pdm-python`, and `.python-version` without using `O_NOFOLLOW` or `lstat` checks. An attacker can provide a malicious repository containing these files as symlinks pointing to sensitive locations on the victim's filesystem. When the victim executes PDM commands that update local state, PDM will follow the symlink and overwrite the target file with the privileges of the invoking user. For `pdm.toml`, the target must be valid TOML to pass the initial load step, but other sinks do not have this constraint. This has been patched in version 2.27.0.

Affected products

pdm-project pdm < 2.27.0

Identifiers

CVE-2026-47763
GHSA-ghq2-5c67-fprm
PYSEC-2026-2862

Timeline

2026-05-21: disclosed
2026-06-10: patched: Fixed in version 2.27.0
2026-06-10: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.