CVE-2026-50003 is a critical path traversal vulnerability in OFFIS DCMTK affecting clients that use bit-preserving C-GET storage mode, including configurations such as getscu --bit-preserving or DCMSCU_STORAGE_BIT_PRESERVING. A malicious or compromised DICOM server can supply file paths that are not properly constrained to the client-selected output directory, allowing use of both relative traversal sequences such as ../ and absolute paths. As a result, the DCMTK client may create or truncate files outside the intended destination directory during C-GET storage handling.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical path traversal vulnerability in OFFIS DCMTK affecting versions prior to 3.7.0. Successful exploitation could cause DCMTK-based clients to write files outside the intended output directory.
A critical path traversal vulnerability in the OFFIS DCMTK Toolkit that allows a malicious or compromised server to cause a DCMTK client using bit-preserving C-GET storage mode to write files outside the intended output directory.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.