HIGH 7.5

CVE-2026-44628: Worklist Server Denial of Service (CVSS 7.5)

CVE-2026-44628 is a denial-of-service vulnerability affecting worklist servers that allows an unauthenticated attacker to crash the service by sending a specially crafted query. The attack succeeds only when specific conditions are met: the server must have a valid Called AE Title (an identifier used in DICOM medical imaging protocols), a corresponding storage directory, an expected lockfile, and at least one matching worklist record in the database. Once triggered, the crash renders the worklist service unavailable until manual restart.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weaknesses (CWE)
CWE-843
Affected products
0 configuration(s)
Published / Modified
2026-06-30 / 2026-07-01

NVD description (verbatim)

An 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.

3 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

This vulnerability stems from improper type handling in worklist server query processing, classified under CWE-843 (Access of Resource Using Incompatible Type). An attacker can supply a malformed query that causes the server to mishandle data types during processing, leading to an unhandled exception or memory violation that crashes the process. The vulnerability requires network access but no authentication, making it remotely exploitable by any actor with network visibility to the worklist port. The crash is reliable and reproducible when the prerequisite server conditions are present.

Business impact

Worklist servers are critical infrastructure in healthcare environments, coordinating diagnostic procedures and patient workflows. A denial-of-service attack disrupts scheduling, delays patient care, and forces operational teams into reactive recovery mode. In high-volume imaging centers, even brief outages can cascade into extended delays. Organizations cannot rely on automatic recovery; manual intervention is required to restart the service. The lack of authentication requirements means the attack surface includes any network path to the worklist service, whether internal or—in misconfigured deployments—external.

Affected systems

No specific vendor or product information is available in the current advisory. Organizations operating DICOM-compliant worklist servers should assume potential exposure and verify compatibility with their specific implementations. Worklist servers are commonly deployed in radiology information systems (RIS), enterprise imaging platforms, and healthcare IT networks. The vulnerability's reliance on specific server conditions (valid AE Title, storage directory, lockfile, and existing records) means not all instances may be exploitable, but this should not be assumed without testing.

Exploitability

Exploitation is straightforward and requires only network access to the worklist service port and knowledge of a valid Called AE Title—information often discoverable through network scanning or reconnaissance. No authentication, no complex setup, and no user interaction is needed. The attacker need only craft and send a single malformed query. Reliable reproduction depends on the target server state; however, most production worklist servers maintain the required conditions (valid AE Title, storage directory, lockfile, and records) as part of normal operation. This is a low-complexity, high-impact attack vector.

Remediation

Apply vendor patches as soon as they become available. Until patching is complete, implement network-level access controls to restrict worklist service ports to authorized imaging and scheduling systems only. Isolate worklist servers on segmented networks, require VPN or firewall rules for access, and monitor for unusual query patterns. Implement service restart automation and alerting to minimize downtime if exploitation occurs. Verify patching against vendor advisories and security bulletins, as no specific patch versions are currently identified in public guidance.

Patch guidance

Contact your worklist server vendor for security updates addressing CVE-2026-44628. Patches may be released as hotfixes, minor version updates, or service packs depending on vendor release cycles. Establish a test environment matching your production configuration, validate patches against the vulnerability conditions (AE Title, storage directory, lockfile, and worklist records), and schedule deployment during low-demand periods to minimize impact on clinical workflows. Verify patch application by confirming version updates and re-testing with known attack queries in a controlled lab setting.

Detection guidance

Monitor worklist server logs for unexpected crashes, restarts, or error messages related to query processing failures. Implement network-based detection for malformed DICOM queries or unusual query patterns directed at worklist ports. Alert on repeated failed queries from the same source, which may indicate reconnaissance or attack attempts. Baseline normal worklist traffic (query frequency, size, syntax patterns) and flag significant deviations. Log and review any service restarts initiated outside of scheduled maintenance windows. DICOM protocol analyzers or packet capture tools can help identify suspicious query structures.

Why prioritize this

A CVSS score of 7.5 (HIGH severity) reflects the vulnerability's network accessibility, lack of authentication requirements, and direct impact on service availability. While confidentiality and integrity are not compromised, the denial-of-service impact on critical healthcare infrastructure justifies urgent attention. The simplicity of exploitation and the reliability of the attack in production environments elevate practical risk beyond the base score. Healthcare organizations should prioritize patching ahead of less critical systems.

Risk score, explained

The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) reflects: Network-based attack vector with no privilege requirements and low attack complexity; no impact on confidentiality or integrity; but high impact on availability. The score of 7.5 appropriately captures a serious but contained threat—not the highest severity, but sufficient to warrant rapid remediation. Organizations should weight business criticality and network exposure when translating this score into internal risk ratings; a worklist server serving a large clinical network may warrant treat-as-critical prioritization despite the base HIGH rating.

Frequently asked questions

Does this vulnerability affect my system if worklist records don't exist in my database?

No. The vulnerability requires at least one matching worklist record to be present. If your server is empty or has no records matching the Called AE Title, the conditions for exploitation are not met. However, most production worklist servers maintain active records, so this is not a reliable safeguard.

Can this vulnerability be exploited from the internet, or only from internal networks?

The vulnerability is remotely exploitable over any network path to the worklist service. If the service is exposed to the internet or accessible from untrusted networks, the risk is significantly higher. Proper network segmentation and firewall rules are essential controls.

What happens if the worklist service crashes? Will it restart automatically?

The vulnerability causes a crash that requires manual restart in most deployments. There is no automatic recovery unless your environment includes service restart automation (e.g., systemd, container orchestration, or redundant failover systems). Until patched, you should implement automated alerts and restart monitoring to reduce recovery time.

How do I know if someone has exploited this vulnerability against my worklist server?

Look for unexplained service crashes or restarts, unusual error messages in worklist logs related to query processing, and any correlation with suspicious network traffic. Enable detailed query logging if available, and review logs for malformed or anomalous requests prior to crashes. Network monitoring and DICOM protocol analysis tools can help identify attack patterns.

This analysis is provided for informational purposes and reflects publicly available information as of the publication date. No specific vendor, product, or patch information is confirmed in the source advisory; organizations must verify against their vendors' official security bulletins. This explainer does not constitute professional security advice. Organizations should conduct their own risk assessments, consult with their security teams, and test patches in controlled environments before production deployment. SEC.co disclaims liability for decisions made based on this analysis. DICOM and medical imaging system security requires specialized expertise; engage healthcare IT security specialists if needed. Source: NVD (public-domain), retrieved 2026-08-09. Analysis generated by SEC.co (claude-haiku-4-5).