# pydicom has a path traversal in FileSet/DICOMDIR ReferencedFileID allows file access outside the File-set root

Advisory record · `GHSA-v856-2rf8-9f28`

- **Identifiers:** `GHSA-v856-2rf8-9f28` · `CVE-2026-32711` · `PYSEC-2026-2266`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 20 Mar 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 20 Mar 2026, 15:57 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `pydicom` (PyPI): affected `>=3.0.0, <3.0.2 || <2.4.5`; fixed in `3.0.2`, `2.4.5`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> pydicom versions below 2.4.5 and from 3.0.0 up to (but not including) 3.0.2 are vulnerable to a path traversal in FileSet handling. A crafted DICOMDIR can set ReferencedFileID to a path outside the File-set root, and FileSet operations such as copy(), write() and remove() then read, copy, move or delete files outside that root. An attacker needs to supply a malicious DICOMDIR, for example by uploading a File-set to an application that loads it with FileSet. Upgrade to pydicom 2.4.5 or 3.0.2. The source gives no workaround besides upgrading.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0032, the 25th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:04 UTC: First seen by agentprime
- 31 Oct 2026, 15:04 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-v856-2rf8-9f28)

## Sources

- [GitHub Advisory Database: GHSA-v856-2rf8-9f28](https://github.com/advisories/GHSA-v856-2rf8-9f28)
- [OSV: GHSA-v856-2rf8-9f28](https://osv.dev/vulnerability/GHSA-v856-2rf8-9f28)
- <https://github.com/pydicom/pydicom/security/advisories/GHSA-v856-2rf8-9f28>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-32711>
- <https://github.com/pydicom/pydicom/commit/6414f01a053dff925578799f5a7208d2ae585e82>
- <https://github.com/pydicom/pydicom>
- <https://github.com/pydicom/pydicom/releases/tag/v3.0.2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-v856-2rf8-9f28>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-v856-2rf8-9f28/>. Everything for agents: <https://agentprime.io/llms.txt>.
