Debian Package Tracker
Register | Log in
Subscribe

pydicom

Choose email to subscribe with

general
  • source: pydicom (main)
  • version: 3.0.2-2
  • maintainer: Debian Med Packaging Team (archive) (DMD) (LowNMU)
  • uploaders: Yaroslav Halchenko [DMD] – Michael Hanke [DMD]
  • arch: all
  • std-ver: 4.7.4
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 2.0.0-1
  • oldstable: 2.3.1-1
  • stable: 2.4.3-2
  • testing: 2.4.3-3
  • unstable: 3.0.2-2
versioned links
  • 2.0.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.3.1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.4.3-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.4.3-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 3.0.2-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • python-pydicom-doc
  • python3-pydicom
action needed
1 security issue in forky high

There is 1 open security issue in forky.

1 important issue:
  • CVE-2026-32711: 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.
Created: 2026-03-21 Last update: 2026-05-12 23:30
Does not build reproducibly during testing normal
A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!
Created: 2024-02-06 Last update: 2026-05-16 07:02
1 low-priority security issue in bookworm low

There is 1 open security issue in bookworm.

1 issue left for the package maintainer to handle:
  • CVE-2026-32711: (needs triaging) 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.

You can find information about how to handle this issue in the security team's documentation.

Created: 2026-03-21 Last update: 2026-05-12 23:30
testing migrations
  • excuses:
    • Migration status for pydicom (2.4.3-3 to 3.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
    • Issues preventing migration:
    • ∙ ∙ Autopkgtest for dcmstack/0.9-3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Reference test triggered, but real test failed already ♻, loong64: Reference test triggered, but real test failed already ♻, ppc64el: Regression ♻ (reference ♻), riscv64: Reference test triggered, but real test failed already ♻, s390x: Test triggered
    • ∙ ∙ Autopkgtest for dcmtk/3.7.0+really3.7.0-1: amd64: Pass, arm64: Pass, i386: Pass, loong64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for pydicom/3.0.2-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, loong64: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: Test triggered
    • ∙ ∙ Autopkgtest for spyder-kernels/3.1.3-3: amd64: Pass, arm64: Pass, i386: Pass, loong64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test triggered
    • ∙ ∙ Too young, only 3 of 5 days old
    • Additional info (not blocking):
    • ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydicom.html
    • ∙ ∙ Reproduced on amd64 - info
    • ∙ ∙ Reproduced on arm64 - info
    • ∙ ∙ Reproduced on armhf - info
    • ∙ ∙ Reproduced on i386 - info
    • Not considered
news
[rss feed]
  • [2026-05-12] Accepted pydicom 3.0.2-2 (source) into unstable (Karsten Schöke)
  • [2026-05-08] Accepted pydicom 3.0.2-1 (source) into unstable (Karsten Schöke)
  • [2025-12-25] pydicom 2.4.3-3 MIGRATED to testing (Debian testing watch)
  • [2025-12-19] Accepted pydicom 2.4.3-3 (source) into unstable (Étienne Mollier)
  • [2025-04-25] pydicom 2.4.3-2 MIGRATED to testing (Debian testing watch)
  • [2025-04-14] Accepted pydicom 2.4.3-2 (source) into unstable (Étienne Mollier)
  • [2024-01-31] pydicom 2.4.3-1 MIGRATED to testing (Debian testing watch)
  • [2024-01-26] Accepted pydicom 2.4.3-1 (source) into unstable (Nilesh Patra)
  • [2023-11-30] pydicom REMOVED from testing (Debian testing watch)
  • [2022-12-04] pydicom 2.3.1-1 MIGRATED to testing (Debian testing watch)
  • [2022-11-28] Accepted pydicom 2.3.1-1 (source) into unstable (Andreas Tille)
  • [2022-07-21] pydicom 2.3.0-1 MIGRATED to testing (Debian testing watch)
  • [2022-07-16] Accepted pydicom 2.3.0-1 (source) into unstable (Andreas Tille)
  • [2021-12-16] pydicom 2.2.2-1 MIGRATED to testing (Debian testing watch)
  • [2021-12-11] Accepted pydicom 2.2.2-1 (source) into unstable (Andreas Tille)
  • [2021-11-07] pydicom 2.0.0-2 MIGRATED to testing (Debian testing watch)
  • [2021-11-02] Accepted pydicom 2.0.0-2 (source) into unstable (Nilesh Patra)
  • [2020-07-24] pydicom 2.0.0-1 MIGRATED to testing (Debian testing watch)
  • [2020-07-17] Accepted pydicom 2.0.0-1 (source) into unstable (Andreas Tille)
  • [2020-01-28] pydicom 1.4.1-1 MIGRATED to testing (Debian testing watch)
  • [2020-01-23] Accepted pydicom 1.4.1-1 (source) into unstable (Andreas Tille)
  • [2018-11-29] pydicom 1.2.1-1 MIGRATED to testing (Debian testing watch)
  • [2018-11-24] Accepted pydicom 1.2.1-1 (source all) into unstable (Yaroslav Halchenko)
  • [2018-10-26] pydicom REMOVED from testing (Debian testing watch)
  • [2018-07-11] pydicom 1.1.0-2 MIGRATED to testing (Debian testing watch)
  • [2018-07-06] Accepted pydicom 1.1.0-2 (source all) into unstable, unstable (Yaroslav Halchenko)
  • [2018-01-26] pydicom 0.9.9-3 MIGRATED to testing (Debian testing watch)
  • [2018-01-20] Accepted pydicom 0.9.9-3 (source) into unstable (Andreas Tille)
  • [2015-09-18] pydicom 0.9.9-2 MIGRATED to testing (Britney)
  • [2015-09-12] Accepted pydicom 0.9.9-2 (source all) into unstable, unstable (Michael Hanke)
  • 1
  • 2
bugs [bug history graph]
  • all: 0
links
  • homepage
  • lintian
  • buildd: logs, reproducibility
  • popcon
  • browse source code
  • other distros
  • security tracker
  • debian patches
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 2.4.3-3

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing