CVE-2026-32711 json
pydicom: Path traversal in FileSet/DICOMDIR ReferencedFileID allows file access outside the File-set root
published 2026-03-20 7 mo ago modified 2026-07-13 3 mo ago also GHSA-v856-2rf8-9f28 , PYSEC-2026-2266 , EUVD-2026-13433
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
pydicom is a pure Python package for working with DICOM files. Versions 2.0.0-rc.1 through 3.0.1 are vulnerable to Path Traversal through a maliciously crafted DICOMDIR ReferencedFileID when it is set to a path outside the File-set root. pydicom resolves the path only to confirm that it exists, but does not verify that the resolved path remains under the File-set root. Subsequent public FileSet operations such as copy(), write(), and remove()+write(use_existing=True) use that unchecked path in file I/O operations. This allows arbitrary file read/copy and, in some flows, move/delete outside the File-set root. This issue has been fixed in version 3.0.2.
Patch / fix
- pypi pydicom 2.4.5, 3.0.2
- pydicom pydicom 3.0.2
- pydicom Debian 14 3.0.2-1
debian advisories DEBIAN-CVE-2026-32711
- python-pydicom openSUSE Tumbleweed 3.0.2-1.1
opensuse advisories openSUSE-SU-2026:10412-1
- py3-pydicom Alpine 3.24, Alpine 3.23 3.0.2-r0
alpine advisories ALPINE-CVE-2026-32711
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 7 mo ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/pydicom/pydicom/security/advisories/GHSA-v856-2rf8-9f28 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | pydicom | >=3.0.0, <3.0.2 <2.4.5 >=2.0.0, <3.0.2 |
3.0.2 2.4.5 |
Affected products
- pydicom pydicom
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/pydicom/pydicom/commit/6414f01a053dff925578799f5a7208d2ae585e82
web, patch
-
github.com
/pydicom/pydicom/security/advisories/GHSA-v856-2rf8-9f28
web, exploit, vendor-advisory, evidence
-
github.com
/pydicom/pydicom/releases/tag/v3.0.2
web, product, release-notes, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-32711
advisory
-
github.com
/pydicom/pydicom
package
Sources
- CVE List CVE-2026-32711
- GitHub Advisory GHSA-v856-2rf8-9f28
- NVD CVE-2026-32711
- OSV PYSEC-2026-2266
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.