IM
IronMonkey Threat Research
‹ Back to ICS Advisories

J4Care dcm4che

CRITICAL
CVSS 9.1
Date 2026-10-15T06:00:00+00:00
Source cisa-csaf
Published by CISA

// Description

Successful exploitation of these vulnerabilities could allow an attacker to delete stored medical images, disclose patient information, inject forged studies, reassign patient records, overwrite files, and cause a denial-of-service condition.

// Vulnerabilities (6)

CVE ID CVSS Score Severity Description
CVE-2026-107621 7.5 high
JPEGParser can enter an infinite loop while parsing a specially crafted or truncated stream.
CVE-2026-101021 7.5 high
MultipartInputStream performs inefficient boundary matching and unnecessary buffer copying. Crafted multipart input can force excessive boundary comparisons and repeated copying.
CVE-2026-105667 7.5 high
In the default configuration, the HL7 listener accepts ADT^A40 patient-merge messages without authenticating the sending application. A remote sender can reassign studies and related workflow records from one patient identity to another. The archive's unmerge does not reverse this.
CVE-2026-97851 9.1 critical
The storage status-change REST service allows location records still associated with DICOM instances to be changed to deletion-related states. Changing a location to TO_DELETE causes PurgeStorageScheduler to delete the referenced object from storage even though the corresponding instance record remains in the database.
CVE-2026-105279 9.1 critical
In the default configuration, the archive accepts DICOM associations from an unregistered calling AE. A remote peer can use C-FIND and C-GET to enumerate and retrieve patient information and medical images. It can also use C-STORE to file fabricated study content under an existing patient identity.
CVE-2026-105273 7.5 high
MP4Parser does not adequately validate MP4 box sizes. A malformed box can cause parsing to make no forward progress and repeatedly process the same input.

// Remediations (1)

Mitigation: J4Care has provided a fix for the vulnerabilities. J4Care recommends users implement release 5.35.2
J4Care has provided a fix for the vulnerabilities. J4Care recommends users implement release 5.35.2 or later.

// References