CVE-2026-44628
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 · uneditedAn unauthenticated attacker can crash the worklist server with a single crafted query when the server has a valid Called AE Title / storage directory, the expected lockfile, and at least one matching worklist record.
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 · moderate confidenceA denial-of-service vulnerability exists in a DICOM worklist server where an unauthenticated attacker can cause a crash by sending a single specially crafted query. Successful exploitation requires the server to have a valid Called AE Title configured with a storage directory, the expected lockfile present, and at least one matching worklist record in the database.
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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 a DICOM worklist server is runningCheck running processes or services for DICOM worklist server components. Look for processes listening on DICOM ports (typically 104, 11112, or custom ports). Consult system documentation or check configuration files for worklist service definitions.Affected if A DICOM worklist server service is active and listening for connections
-
Verify if a valid Called AE Title is configuredExamine the DICOM worklist server configuration files for the Called AE Title setting. This is typically found in the server's main configuration file under DICOM settings or AE (Application Entity) configuration sections.Affected if A valid Called AE Title is explicitly configured in the server settings
-
Confirm a storage directory is configuredInspect the server configuration for a storage directory or storage path setting. This is often labeled as 'Storage Directory', 'Worklist Storage Path', or similar in the DICOM configuration section.Affected if A storage directory path is defined and accessible to the server process
-
Check for the presence of the lockfileSearch the server's working directory, configuration directory, or data directory for the lockfile expected by the worklist server. Consult product documentation for the expected lockfile name and default locations.Affected if The required lockfile exists in the expected location and is readable by the server
-
Query the worklist database for recordsAccess the worklist database (SQL, file-based, or other) and verify if any worklist records exist. Use database query tools or the server's administrative interface to list worklist entries.Affected if The database contains at least one active worklist record that could match a query
A system is affected by this CVE only when all four prerequisites are met simultaneously: a valid Called AE Title is configured, a storage directory is set, the required lockfile exists, and at least one worklist record exists in the database.
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 robust input validation on all DICOM query parameters and add exception handling around query processing logic to prevent crashes from malformed input. Consider rate limiting or IP-based access controls on the worklist service until a patch is available.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44628 — 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-44628 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