CVE-2026-105667 J4Care CVE debrief

Who should care

Healthcare organizations using dcm4chee-arc-light for patient data management should assess their exposure and verify the configuration of their systems. System administrators need to verify and adjust the configuration of dcm4chee-arc-light systems to prevent exploitation. Healthcare organizations may face regulatory compliance issues due to potential patient data breaches. Patient data integrity may be compromised due to unauthorized reassignment of and

Why it matters

CVE-2026-105667 is a high-severity vulnerability in J4Care dcm4chee-arc-light that allows remote attackers to reassign patient studies and workflow records without authentication. Healthcare organizations should assess their exposure, verify system configurations, and take necessary remediation steps to prevent potential patient data breaches and regulatory compliance issues.

• Patient data integrity may be compromised due to unauthorized reassignment of studies and workflow records
• Healthcare organizations may face regulatory compliance issues due to potential patient data breaches
• System administrators need to verify and adjust the configuration of dcm4chee-arc-light systems to prevent exploitation

Technical summary

The HL7 listener in J4Care dcm4chee-arc-light accepts ADT^A40 patient-merge messages without authentication, allowing remote reassignment of studies and workflow records. This vulnerability has a high CVSS score of 7.5 and is classified as HIGH severity. The vulnerability allows a remote sender to reassign studies and related workflow records from one patient identity to another. The archive's unmerge does not reverse this. Defenders should prioritize verifying the configuration of dcm4chee-arc-light systems, especially those handling sensitive patient data, and ensure that authentication is properly enabled for the HL7 listener.

Defensive priority

Defenders should prioritize verifying the configuration of dcm4chee-arc-light systems, especially those handling sensitive patient data, and ensure that authentication is properly enabled for the HL7 listener.

Recommended defensive actions

• Verify the configuration of dcm4chee-arc-light systems to ensure authentication is enabled for the HL7 listener
• Review patient data handling procedures to prevent unauthorized reassignment of studies and workflow records
• Monitor system logs for suspicious activity related to patient-merge messages
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE Program record and NVD vulnerability detail provide information on the vulnerability. However, details on affected versions and remediation are limited. The CVE record was published on 2026-10-16T14:32:22.216Z and has not been modified since then. The source item provides details on the vulnerability but does not specify affected versions or remediation steps. Supplemental sources may provide additional information.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.