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.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2026-47763)

Note that Nessus relies on the presence of the package as reported by the vendor.

The remote openSUSE 16 host has a package installed that is affected by multiple vulnerabilities as referenced in the openSUSE-SU-2026:21161-1 advisory.

    Changes in python-pdm:

    - CVE-2026-47763: Do not follow symlinks when writing config files (bsc#1268384)
    - CVE-2026-47763: Do not write to paths outside the scheme dir (bsc#1268385)
    - CVE-2026-47781: Update plugin installation path to use project_plugins_dir (bsc#1268386)

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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. (CVE-2026-47763)

ID	Name	Product	Family	Type	Severity
332063	Linux Distros Unpatched Vulnerability : CVE-2026-47763	Nessus	Misc.	Local	medium
324056	openSUSE 16 Security Update : python-pdm (openSUSE-SU-2026:21161-1)	Nessus	SuSE Local Security Checks	Local	high
443061	SCA: security update for pdm (GHSA-ghq2-5c67-fprm)	Tenable Cloud Security	SCA Checks	Local	medium
443061	SCA: security update for pdm (GHSA-ghq2-5c67-fprm)	Tenable Self-Hosted Container Security	SCA Checks	Local	medium

Detections

Analytics

CVE-2026-47763

medium

Tenable Plugins

medium

high

medium

medium