high CVSS 7.8 EPSS <0.1%

CVE-2026-32711·Python vulnerability

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.

Severity
high
Software
Python
Fixed in
3.0.2
Published

How likely is exploitation

FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at <0.1% — in the bottom 1% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.

Read the two together. CVE-2026-32711 scores 7.8 on CVSS, so a successful attack would be serious — but at <0.1%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.

Affected versions

From: 2.0.0

Until: 3.0.2

Fixed in: 3.0.2

How to fix this CVE

Update pydicom to version 3.0.2 or later to patch a path traversal vulnerability in DICOMDIR file handling. The vulnerability allows attackers to read, copy, or delete files outside the intended File-set root directory through maliciously crafted DICOM files. Ensure all Python environments using pydicom are upgraded immediately, especially if processing untrusted DICOM files.

sudo dnf update python3-pydicom

Defensia detects this vulnerability

How to check if you are affected

  1. Run `python3 -c "import pydicom; print(pydicom.__version__)"` to check the installed pydicom version
  2. Verify if pydicom is installed: `pip3 show pydicom | grep Version` or `rpm -qa | grep pydicom`
  3. Search application logs for file access patterns involving DICOMDIR parsing: `grep -r "DICOMDIR\|ReferencedFileID" /var/log/application.log`
  4. Confirm the patch was applied by re-running `python3 -c "import pydicom; print(pydicom.__version__)"` and verifying version >= 3.0.2

FAQ

What is CVE-2026-32711?

CVE-2026-32711 is a path traversal vulnerability in pydicom's DICOMDIR file handling that allows attackers to access files outside the designated File-set root directory by crafting malicious ReferencedFileID paths. This can lead to unauthorized file reads, copies, and deletions on the affected system.

Is CVE-2026-32711 being actively exploited?

No, this vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available. However, the high CVSS score (7.8) indicates significant risk if exploited.

What versions of Python are affected by CVE-2026-32711?

The vulnerability affects pydicom versions 2.0.0 through 3.0.1. Python itself is not directly vulnerable; the issue resides in the pydicom library. Any system running Python with an affected pydicom version is at risk.

How do I check if my server is vulnerable to CVE-2026-32711?

Run `pip3 show pydicom | grep Version` and check if the version is between 2.0.0 and 3.0.1 (inclusive). If so, your system is vulnerable and requires an immediate upgrade to version 3.0.2 or later.

Does Defensia detect CVE-2026-32711?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If pydicom is installed on a monitored server, CVE-2026-32711 will appear in your dashboard with remediation steps.

Related Python CVEs

CVE-2026-28505CVSS 10Tautulli is a Python based monitoring and tracking tool for Plex Media Server. Prior to version 2.17.0, the str_eval() function in notification_handler.py implements a sandboxed eval() for notification text templates. The sandbox attempts to restrict callable names by inspecting code.co_names of the compiled code object. However, co_names only contains names from the outer code object. When a lambda expression is used, it creates a nested code object whose attribute accesses are stored in code.co_consts, NOT in code.co_names. The sandbox never inspects nested code objects. This issue has been patched in version 2.17.0.
CVE-2026-25632CVSS 10EPyT-Flow is a Python package designed for the easy generation of hydraulic and water quality scenario data of water distribution networks. Prior to 0.16.1, EPyT-Flow’s REST API parses attacker-controlled JSON request bodies using a custom deserializer (my_load_from_json) that supports a type field. When type is present, the deserializer dynamically imports an attacker-specified module/class and instantiates it with attacker-supplied arguments. This allows invoking dangerous classes such as subprocess.Popen, which can lead to OS command execution during JSON parsing. This also affects the loading of JSON files. This vulnerability is fixed in 0.16.1.
CVE-2026-33054CVSS 10Mesop is a Python-based UI framework that allows users to build web applications. Versions 1.2.2 and below contain a Path Traversal vulnerability that allows any user supplying an untrusted state_token through the UI stream payload to arbitrarily target files on the disk under the standard file-based runtime backend. This can result in application denial of service (via crash loops when reading non-msgpack target files as configurations), or arbitrary file manipulation. This vulnerability heavily exposes systems hosted utilizing FileStateSessionBackend. Unauthorized malicious actors could interact with arbitrary payloads overwriting or explicitly removing underlying service resources natively outside the application bounds. This issue has been fixed in version 1.2.3.
CVE-2026-34938CVSS 10PraisonAI is a multi-agent teams system. Prior to version 1.5.90, execute_code() in praisonai-agents runs attacker-controlled Python inside a three-layer sandbox that can be fully bypassed by passing a str subclass with an overridden startswith() method to the _safe_getattr wrapper, achieving arbitrary OS command execution on the host. This issue has been patched in version 1.5.90.
CVE-2026-26030CVSS 9.9Semantic Kernel, Microsoft's semantic kernel Python SDK, has a remote code execution vulnerability in versions prior to 1.39.4, specifically within the `InMemoryVectorStore` filter functionality. The problem has been fixed in version `python-1.39.4`. Users should upgrade this version or higher. As a workaround, avoid using `InMemoryVectorStore` for production scenarios.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-32711. Free for 1 server.

Get started free