CVE-2026-47763

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 95% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.8
EG Score
6.8(medium)
EG Risk
47(Track)
EG Risk 47/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity68% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

June 10, 2026

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated Aug 4, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
github_release Patch Available

v2.27.0

Patch available: pdm-project/pdm 2.27.0

https://github.com/pdm-project/pdm/releases/tag/2.27.0
github Patch Available🟡 PoC Available

Project-Local State and Config Writes Follow Symlinks · Advisory · pdm-project/pdm · GitHub

https://github.com/pdm-project/pdm/security/advisories/GHSA-ghq2-5c67-fprm

Vendor Advisories for CVE-2026-47763(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
pdm2.2.1+ds1-1 ... 2.28.0-1 (14 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
pdm2.20.1+ds1-2 ... 2.28.0-1 (9 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pdm2.20.1+ds1-2 ... 2.26.6-1 (7 versions)2.27.0-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
pdm0.0.0 ... 2.9.3 (247 versions)2.27.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-25 00:19 UTCEG score recompute
  3. 2026-08-23 10:46 UTCEG score recompute
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 17:55 UTCEG score recompute
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 17:16 UTCEG score recompute
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 14:56 UTCEG score recompute
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 00:04 UTCEG score recompute
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 23:55 UTCEG score recompute
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-13 22:16 UTCEG score recompute
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-12 20:11 UTCEG score recompute
  21. 2026-08-12 13:51 UTCEPSS rescore
  22. 2026-08-11 20:07 UTCEG score recompute
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-09 16:56 UTCEG score recompute
  25. 2026-08-09 13:46 UTCEPSS rescore
Show 16 more
  1. 2026-08-07 16:46 UTCEG score recompute
  2. 2026-08-06 16:41 UTCEG score recompute
  3. 2026-08-06 13:47 UTCEPSS rescore
  4. 2026-08-05 19:17 UTCEPSS rescore
  5. 2026-08-05 16:32 UTCEG score recompute
  6. 2026-08-05 15:31 UTCEG score recompute
  7. 2026-08-04 18:26 UTCEG score recompute
  8. 2026-08-04 17:51 UTCEG score recompute▲ 6.80
  9. 2026-08-04 17:46 UTCMITRE cvelistV5CVSS v3 → 6.8 · CVSS v4 → 6.8
  10. 2026-08-01 10:09 UTCEG score recompute
  11. 2026-07-26 20:56 UTCEG score recompute
  12. 2026-07-23 03:17 UTCEG score recompute
  13. 2026-06-14 23:18 UTCEPSS rescore
  14. 2026-06-13 23:00 UTCEPSS rescore
  15. 2026-06-12 23:12 UTCEPSS rescore
  16. 2026-06-10 21:17 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-47763?
CVE-2026-47763 is a medium vulnerability published on June 10, 2026. 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…
When was CVE-2026-47763 disclosed?
CVE-2026-47763 was first published in the National Vulnerability Database on June 10, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47763 actively exploited?
CVE-2026-47763 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.5% of all scored CVEs.
What is the CVSS score of CVE-2026-47763?
CVE-2026-47763 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-47763?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47763, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47763

Explore →

Is Your Infrastructure Affected by CVE-2026-47763?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs