CVE-2026-50003
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA malicious or compromised server can make a DCMTK client using bit-preserving C-GET storage mode write files outside the chosen output directory, using both relative (../) paths and absolute paths.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDCMTK's DICOM C-GET client in bit-preserving storage mode lacks proper path validation, allowing a malicious server to send file path references containing path traversal sequences (../) or absolute paths. This causes the client to write files outside the intended output directory, enabling arbitrary file write and potential code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed DCMTK versionRun 'dcmtk-version' or check package manager for DCMTK packages; compare the version number to any known affected releasesAffected if The installed version is within the range that includes the fix for CVE-2026-50003 but the system has not been patched
-
Confirm C-GET client is in useReview application logs or configuration for usage of the 'storescp' or 'c-get' services in bit-preserving storage mode; check for command-line invocations using the '--bit-preserving' flagAffected if The C-GET client is actively used with bit-preserving storage enabled
-
Verify output directory configurationInspect the configuration file or command parameters that specify the output directory for received DICOM files; look for the '--output-directory' or similar parameter in the C-GET storage provider setupAffected if An output directory is configured without restrictive path validation rules
-
Test for path traversal vulnerabilityIf possible, send a test DICOM file with a manipulated Storage Filepath or SOP Instance UID containing '../' sequences or an absolute path, then verify if files are written outside the designated output directoryAffected if Files are written outside the intended output directory when path traversal sequences are present
A user is affected if they run DCMTK's C-GET client in bit-preserving storage mode without having applied the path validation fix, allowing arbitrary file writes outside the configured output directory.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict path validation in the C-GET storage provider to canonicalize paths and reject any that escape the designated output directory, ensuring all writes remain within the intended boundary.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50003 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-50003 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data