CVE-2026-47781
PDM loads project-local plugins that allow arbitrary code execution from untrusted checkouts.
Is CVE-2026-47781 being exploited?
Not confirmed. CVE-2026-47781 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.
How severe is CVE-2026-47781?
CVE-2026-47781 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-47781?
Yes. A fix has been recorded for CVE-2026-47781. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-47781 affect?
CVE-2026-47781 affects PDM <= 2.26.9, Python development environments, CI/CD runners, Build servers, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-47781?
Upgrade PDM to 2.27.0; avoid running pdm in untrusted checkouts; audit CI runners
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary code execution as the invoking user via attacker-controlled .pdm-plugins/.pth during pdm init; triggers on simple commands (e.g., pdm --version). High risk in CI/automation.
Immediate action required
- affected< 2.27.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.