CVE-2026-32711 | pydicom: Path traversal in FileSet/DICOMDIR ReferencedFileID allows file access outside the File-set root

Exp

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.

Published: 2026-03-20 Last update: 2026-03-23 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-32711 is rated Exploit Available (50/100): CVSS High severity, with low exploitation likelihood (EPSS 0.02%). Core evidence: 1 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2026-32711

EDB-ID Source Kind Published Link
nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2026-32711

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-20 0.02%

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-32711

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8 5.9 [email protected]

Weakness enumeration for CVE-2026-32711

GitHub Security Advisory for CVE-2026-32711

GHSA-v856-2rf8-9f28 · Severity: high · Ecosystem: pip — pydicom has a path traversal in FileSet/DICOMDIR ReferencedFileID allows file access outside the File-set root

OS Trackers for CVE-2026-32711

vendor priority summary link
alpine CVE-2026-32711: 1 source package rows (py3-pydicom); 4 state rows across 2 repos (3.23-community, edge-community); fixed 2, open 2. https://security.alpinelinux.org/vuln/CVE-2026-32711
debian not yet assigned CVE-2026-32711 not yet assigned priority: Debian including 1 source packages (pydicom), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 4, resolved 1. https://security-tracker.debian.org/tracker/CVE-2026-32711
ubuntu medium CVE-2026-32711 medium priority: Ubuntu including 1 source packages (pydicom), 7 status rows across 7 suites (bionic, focal, jammy, noble, questing, upstream, xenial): needs-triage 7. https://ubuntu.com/security/CVE-2026-32711

Affected software / configurations for CVE-2026-32711

Vendor Product Version Raw CPE
pydicom pydicom >= 2.0.0, < 3.0.2 cpe:2.3:a:pydicom:pydicom:*:*:*:*:*:python:*:*

References for CVE-2026-32711

cvelogic Threat Intelligence