Vulnerability in pdm (CVE-2026-47763)
Summary
Vulnerability in pdm (CVE-2026-47763). Risk of unauthorized operations or information disclosure. Exploitable via pdm.toml. Mitigation: upgrade to 2.27.0 or later.
Original description
The description as published by the source.
Summary
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.
Affected Behavior
- Project-local config writes can affect files outside the repository
- The most stable demonstrated sink is
pdm.toml - Related sinks include
.pdm-pythonand.python-version
Affected Code
src/pdm/project/config.py:303-350src/pdm/project/core.py:209-217src/pdm/cli/commands/use.py:187-189
Technical Details
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.
Impact
- Arbitrary file clobber as the invoking user
- Destructive modification of local files outside the repository root
- Useful primitive for privilege abuse when
pdmis run in eleva…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47763 has been found in pdm.
Attackers can target a specific entry point like pdm.toml over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade pdm to 2.27.0 or later.
If unsure, ask your IT team or search "pdm CVE-2026-47763" on the vendor's site.
CVE-2026-47763 (pdm) — CWE-61
Attack surface: pdm.toml / lstat / O_NOFOLLOW / pdm
Patched: 2.27.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-61) exists in pdm. Attackers reach the vulnerable code path via pdm.toml.
Check the vendor advisory for the affected versions of pdm. Attack surface: pdm.toml / lstat / O_NOFOLLOW / pdm.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.27.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'pdm' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pdm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pdmを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade pdm to 2.27.0ステージング環境で 2.27.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-47763 pdm
References
- package github.com
- web github.com
- web github.com
- web github.com