Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-47781

Code Injection in pdm (CVE-2026-47781)

Summary

Code injection in pdm (CVE-2026-47781). Risk of unauthorized operations or information disclosure. Exploitable via Core. Mitigation: upgrade to 2.27.0 or later.

Original description

The description as published by the source.

Summary

PDM automatically loads project-local plugin paths from .pdm-plugins during Core initialization. Because this path is added via site.addsitedir(), attacker-controlled .pth files inside the project plugin directory are processed and can execute Python code before normal CLI handling begins.

This allows arbitrary code execution with the privileges of the user running pdm from an untrusted repository checkout.

Affected Behavior

  • Trigger does not require pdm install --plugins
  • A low-impact command such as pdm --version is sufficient
  • Impact is strongest in CI, privileged shells, and automation contexts

Affected Code

  • src/pdm/core.py:74-82
  • src/pdm/core.py:310-333
  • src/pdm/core.py:335-352

Technical Details

Core.__init__() calls load_plugins() before ordinary command execution. load_plugins() calls _add_project_plugins_library(), which derives the project-local .pdm-plugins library path and adds it through site.addsitedir().

On CPython, site.addsitedir() processes .pth files found in the added directory. .pth lines beginning with import are executed immediately. This creates a trust-boundary break: project-controlled files execute before the user explicitly opts into plugin installation or plugin loading.

Impact

  • Arbitrary code execution as the invoking user
  • Potential credential theft, persistence, or workspace tampering
  • Potential privilege escalation when pdm is run via sudo, root-owned CI jo…

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-47781 has been found in pdm.
Attackers can target a specific entry point like Core 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-47781" on the vendor's site.

CVE-2026-47781 (pdm) — CWE-94
Attack surface: Core / pdm / sudo / evil.pth
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.

❓ What is the problem

Arbitrary code execution (CWE-94) exists in pdm. Attackers reach the vulnerable code path via Core.

📍 Affected scope

Check the vendor advisory for the affected versions of pdm. Attack surface: Core / pdm / sudo / evil.pth.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.27.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify exposure identify 
    grep -r 'pdm' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で pdm を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade pdm to 2.27.0

    ステージング環境で 2.27.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip pdm
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.27.0"}]}]
PyPI pdm
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.27.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details