Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach network-exposed DICOM/parser endpoint
-
DeliverySubmit crafted or truncated JPEG stream
-
ExploitJPEGParser enters infinite loop
-
ExecutionThread/CPU resource exhaustion
-
ImpactArchive availability degraded or denied
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Loop termination conditions
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to deliver a maliciously crafted or truncated JPEG-encoded stream to dcm4chee-arc-light's JPEGParser - i.e., the deployment must expose a DICOM/image-ingestion path that parses attacker-supplied image data. Per the provided vector (PR:N/UI:N) no authentication or user interaction is required and exploitation works against default behavior, but realistic risk is limited by network reachability: the vulnerable service must be reachable from the attacker's position (untrusted network or internet exposure rather than a segmented clinical VLAN). Impact is confined to availability (VA:H; VC:N/VI:N) - a hang/resource exhaustion, not code execution or data compromise. |
| Impact | The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H) describes a network-reachable, low-complexity, unauthenticated flaw with availability-only impact and no confidentiality or integrity consequence - consistent with the CWE-835 infinite-loop/denial-of-service classification and the 'Denial Of Service' tag. The 8.7 base score is driven almost entirely by the high availability impact combined with the unauthenticated network vector; this is a genuine availability concern but NOT a code-execution or data-breach issue. No EPSS score, no CISA KEV listing, and no public POC are present in the supplied data, so there is no evidence of active or widespread exploitation - exploitation status is therefore 'no public exploit identified at time of analysis.' The signals are internally consistent (network DoS, no conflicting local-access language in the description), so the main caveat is deployment context rather than metric contradiction: real-world priority depends heavily on whether the dcm4chee-arc-light DICOM service is exposed to untrusted networks. For internet- or broadly-network-exposed medical imaging archives this warrants prompt patching; for segmented clinical networks the realistic risk is lower. Note that PR:N assumes the vulnerable parser processes streams without prior authentication, which should be confirmed against the actual DICOM association/service configuration. |
| Exploit ScenarioDerived | An attacker able to reach the dcm4chee-arc-light service over the network sends a specially crafted or truncated JPEG-encoded stream to the JPEGParser, which enters an infinite loop and consumes CPU resources, hanging or starving the processing thread. Repeated or concurrent submissions can degrade or deny availability of the DICOM archive used for medical image storage and retrieval. No public exploit code is identified in the provided data, and the impact is limited to denial of service with no confidentiality or integrity effect. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 16, 2026
JPEGParser in j4care's dcm4chee-arc-light can be driven into an infinite loop by a specially crafted or truncated JPEG-encoded stream delivered to the archive's image/DICOM ingestion path, resulting in a denial-of-service condition (CWE-835). Per the supplied CVSS 4.0 vector the flaw is network-reachable and requires no authentication and no user interaction (AV:N, AC:L, PR:N, UI:N), but the impact is availability-only (VA:H with VC:N/VI:N) - no code execution, data disclosure, or integrity loss is described. No public exploit code and no confirmed active exploitation were identified at time of analysis, and realistic risk is bounded by network reachability: deployments that expose a JPEG/DICOM parsing endpoint beyond a segmented clinical network are the ones materially at risk.
Earlier versions of this analysis (1)
A specially crafted or truncated JPEG stream sent to the JPEGParser component of dcm4chee-arc-light drives the parser into an infinite loop, consuming processing resources and denying availability of the DICOM archive (CVSS 3.1 base 7.5, impact confined to A:H). The assessed vector (AV:N/AC:L/PR:N/UI:N) indicates the bug is reachable over the network with no privileges and no user interaction, meaning any deployment whose DICOM C-STORE, image-ingestion, or upload path routes untrusted payloads through this parser is at risk, with real-world exposure bounded mainly by whether that parsing endpoint is reachable from untrusted networks. There is no public exploit code and no confirmed active exploitation at time of analysis, and no data disclosure or modification is possible - CISA addressed the issue in ICS medical advisory ICSMA-26-288-02.
RemediationAI
No vendor-released patch was identified at time of analysis, so remediation must currently rely on compensating controls; monitor the CISA ICS medical advisory ICSMA-26-288-02 (https://www.cisa.gov/news-events/ics-medical-advisories/icsma-26-288-02) and the associated CSAF feed (https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsma-26-288-02.json) for the vendor's fixed build and apply it as soon as it is published. Until then, restrict network reachability of the DICOM/image-ingestion endpoints: block inbound access to the archive's DICOM and web ports (commonly TCP 104/2762 for DICOM and 8080/8443 for the web UI) from untrusted networks at the firewall, and require clinical clients and modalities to reach the service only from a segmented VLAN or through a VPN - the trade-off is that legitimate remote modality or teleradiology integrations must be explicitly allowlisted or tunnelled. Where the platform allows it, enforce request/connection timeouts, cap concurrent parsing threads or queue depth, and configure upstream proxies or load balancers to drop stalled requests, accepting that aggressive timeouts may terminate legitimate large-image transfers. Because a single stuck thread is enough to exhaust CPU on a vulnerable instance, enable process supervision and automated restart of the affected service (with alerting on hung threads and CPU saturation) so a triggered loop degrades only one worker rather than the whole archive, and pre-process or reject truncated JPEG payloads at the network boundary if an ingest-side content filter is available. These measures reduce exposure but do not eliminate the underlying CWE-835 loop, which only a vendor fix can correct.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is JPEGParser inside dcm4chee-arc-light, the open-source clinical DICOM archive maintained by j4care (identified via CPE cpe:2.3:a:j4care:dcm4chee-arc-light:*:*:*:*:*:*:*:*, i.e. the CPE does not constrain to a fixed version). The root cause class is CWE-835, 'Loop with Unreachable Exit Condition (Infinite Loop)': when the parser processes a malformed or truncated JPEG bitstream - for example one where expected marker segments, length fields, or terminating markers are absent or inconsistent - the decoding/scan loop never satisfies its exit condition. Because the parser continues consuming CPU on a single stuck request thread, the practical effect is resource exhaustion and a service hang rather than memory corruption, which matches the CISA ICS advisory categorization under the 'Denial Of Service' tag and the availability-only impact recorded in the CVSS 4.0 vector. The vulnerability is classified as a network-reachable, low-complexity issue (AV:N/AC:L, PR:N/UI:N) with no confidentiality or integrity consequences, consistent with the independently assessed CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
Know when Dcm4Chee Arc Light gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Network-reachable parser consuming attacker-supplied JPEG data with no auth or interaction (AV:N/AC:L/PR:N/UI:N); infinite loop causes availability-only impact (A:H, C:N/I:N), scope unchanged.
Primary rating from Vendor (icscert).
CVSS VectorVendor: icscert
Lifecycle Timeline
2DescriptionCVE.org
JPEGParser can enter an infinite loop while parsing a specially crafted or truncated stream.
Executive ViewAI
j4care's dcm4chee-arc-light is vulnerable to an unauthenticated network-based denial-of-service attack through its JPEG/DICOM ingestion path, which could disrupt access to medical imaging archives and impact clinical workflows. Leadership should care because the vulnerability is high severity (CVSS 8.7) and no vendor-released patch is currently available, leaving organizations dependent on network segmentation and monitoring until a fix is released. No public exploit identified at time of analysis.
No vendor-released patch identified at time of analysis; interim mitigations include network segmentation, restricting JPEG/DICOM ingestion endpoints to trusted clinical networks, implementing rate limiting and input validation, monitoring for infinite loop patterns, and disabling JPEG ingestion if not essential.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
More in Dcm4Chee Arc Light
View allUnauthenticated remote peers can query and download patient demographics and medical imagery from dcm4chee-arc-light arc
Unauthenticated remote attackers can irreversibly delete stored DICOM objects in dcm4chee-arc-light by invoking the stor
Unauthenticated HL7 ADT^A40 patient-merge messages accepted by the dcm4chee-arc-light archive's default listener let a r
Remote, unauthenticated attackers can exhaust dcm4chee-arc-light by submitting crafted multipart payloads to its Multipa
Malformed MP4 box-size fields submitted to the MP4Parser component in j4care dcm4chee-arc-light drive the parser into a
EUVD-2026-102891
NVD
CVE.org
Vulnrichment
GitHub
Exploit-DB