CVE-2026-56445
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 · uneditedThe qrscp application's C-STORE handler uses a specific instance from attacker-supplied DICOM datasets directly in os.path.join() without sanitization, allowing file writes to arbitrary 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 confidenceThe qrscp application's C-STORE handler contains a path traversal vulnerability where attacker-supplied data from DICOM datasets is used directly in os.path.join() without sanitization, allowing arbitrary file writes to the filesystem.
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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 if qrscp is installedSearch for the qrscp binary or service on the system using 'which qrscp' or by checking installed packages (e.g., dpkg -l, rpm -qa, pip list)Affected if qrscp is present on the system
-
Determine qrscp versionRun 'qrscp --version' or check the package manager for the installed version of the software containing qrscpAffected if The installed version falls within any vulnerable release range (compare to the CVE disclosure date and vendor patch timeline)
-
Verify C-STORE SCP service is enabledCheck qrscp configuration files (commonly in /etc/qrscp.conf, /etc/dicom/, or similar paths) for an active C-STORE SCP (Service Class Provider) service configurationAffected if C-STORE SCP service is enabled and listening for DICOM associations
-
Confirm network exposure of DICOM serviceInspect network listeners (netstat, ss, or lsof) for ports typically used by DICOM C-STORE (e.g., 11112, 104, or custom ports as defined in config)Affected if The DICOM C-STORE port is exposed to untrusted networks or accepts anonymous connections
-
Inspect DICOM storage path configurationReview qrscp configuration for the storage directory setting (look for StorageArea, StorageDir, or similar parameters) and verify whether input validation is applied to incoming dataset pathsAffected if The storage path configuration allows writing to arbitrary locations or lacks path validation on incoming DICOM dataset fields
A system is affected if qrscp with an enabled C-STORE service is running and processing DICOM datasets from untrusted sources without input validation on dataset fields used in path operations.
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 input validation and sanitization on DICOM dataset fields before using them in path operations; use safe path construction methods that prevent directory traversal (e.g., validating against an allowed directory, using os.path.realpath() to resolve and validate paths).
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56445 — 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-56445 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