VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

gdcm: vulnerability history, versions and safety

gdcm is a package in the Debian ecosystem. Vulert records 13 vulnerabilities for it across 44 releases, from Nov -0001 to Dec 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
13 vulnerabilities recorded U13
i
9 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
5 in the last 12 months

Most recent disclosure 16 Dec 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all gdcm vulnerabilities

Vulert verdict on gdcm i

Updated on 23 Oct 2026

Careful: 9 of the 13 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 13 vulnerabilities on record across 2026 years, 5 in the last year.

What to do: Plan around the 9 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 13 over 2026 years · 5 in the last year i
  • Latest disclosure 16 Dec 2025 i
  • Highest CVSS 10.0 i
  • With no published fix 9 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for gdcm, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 44 of 44 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 1
  • 2016 4
  • 2024 3
  • 2025 5

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 5 of the 13 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for gdcm

The 5 most severe of 13 vulnerabilities recorded for this package

Search all 13 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Integer Overflow Vulnerability in GDCM Package Allows Arbitrary Code Execution 10.0 critical 2.6.2-1 12 Jan 2016
Heap Buffer Overflow in GDCM Package: CVE-2024-22373 9.8 critical No fix published 25 Apr 2024
Heap-Based Buffer Overflow in GDCM Package: CVE-2024-22391 9.8 critical No fix published 25 Apr 2024
Out-of-Bounds Read Vulnerability in GDCM Package: CVE-2015-8397 8.2 high 2.6.2-1 12 Jan 2016
Out-of-Bounds Read Vulnerability in Grassroot DICOM (gdcm) - CVE-2025-53618 7.4 high No fix published 16 Dec 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About gdcm

Is gdcm safe to use?

Vulert records 13 vulnerabilities for gdcm in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 13 not yet rated. 9 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does gdcm have?

13 vulnerabilities are recorded for gdcm in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 13 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new gdcm vulnerabilities disclosed?

5 vulnerabilities were recorded for gdcm in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of gdcm are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor gdcm for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the gdcm version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.