CVE-2026-32711: pydicom is a pure Python package for working with DICOM files

Q: How do I fix CVE-2026-32711?

pydicom: upgrade to 3.0.2. Exact commands for each OS are on this page.

Q: Is CVE-2026-32711 being exploited?

CVE-2026-32711 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-32711 affect?

CVE-2026-32711 affects pydicom. Severity is high (CVSS 7.8). 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. py

Q: How urgent is CVE-2026-32711?

Priority 38/100. High severity; Public exploit reference

Routine

HIGH 7.8UPGRADE

CVE-2026-32711 is a high-severity flaw (CVSS 7.8) affecting pydicom. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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()+wri

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 79%)
CISA exploited list	No
Weakness	CWE-22
Published	2026-03-20
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: pydicom

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-20 02:16 UTCPublished CVE record published
2026-06-17 10:36 UTCUpdated Record last modified

pydicom pydicom UPGRADE

Affected: >= 2.0.0 and < 3.0.2

Fixed in: 3.0.2

Safe to downgrade to: a release before 2.0.0

1. Check installed version

pip show pydicom

2. UPGRADE to 3.0.2

pip install --upgrade "pydicom>=3.0.2"

3. If no update is available yet, DOWNGRADE to a release before 2.0.0

pip index versions pydicom pip install "pydicom<2.0.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-32711?

pydicom: upgrade to 3.0.2. Exact commands for each OS are on this page.

Is CVE-2026-32711 being exploited?

CVE-2026-32711 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-32711 affect?

CVE-2026-32711 affects pydicom. Severity is high (CVSS 7.8). 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. py

How urgent is CVE-2026-32711?

Priority 38/100. High severity; Public exploit reference

Software pages

Python vulnerabilities

References

← Back to latest CVEs