Critical path traversal in DCMTK could enable arbitrary file writes in healthcare imaging workflows, risking patient data exposure and operational disruption.
CVE-2026-50003
DCMTK C-GET path traversal allows writing outside output dir.
Is CVE-2026-50003 being exploited?
Not confirmed. CVE-2026-50003 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.66% probability of exploitation in the next 30 days.
How severe is CVE-2026-50003?
CVE-2026-50003 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-50003?
Not known from our data. No patch reference has been recorded for CVE-2026-50003, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-50003 affect?
CVE-2026-50003 affects DCMTK-based DICOM clients, PACS, DICOM viewers/servers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-50003?
Upgrade to patched DCMTK when available; audit deployments and limit C-GET usage
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary file writes via crafted server; potential data exposure and disruption of DICOM workflows.
Patch when possible
- affected<= 3.7.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.