LIVE FEED

A proposed class action accuses University Hospitals of negligence after an October 22 cyberattack that took its MyChart portal offline; the Cleveland patient's suit, filed October 28, claims more than a million records were exposed, a number University Hospitals has not confirmed. University of New Mexico Health Sciences Center disclosed a cyberattack October 26 that diverted ambulances for about two hours; the BYOD extortion group claims it compromised 36,000 systems, a figure UNM has not confirmed. Philips updated its Node2Shell advisory October 27 for CVE-2026-111497, the Node.js Brotli decoder flaw it first flagged October 26 against PIC iX 4.x; the advisory still names no impacted products or fixed version. Philips updated its PHP2Shell advisory October 27 for CVE-2026-109618 and CVE-2026-109619, adding five more affected products including IntelliSpace Portal V12 and Philips Axon to the seven already listed. NorthShore Health Centers disclosed a data breach to patients October 27, one of several Midwest provider notifications issued that week. Denver Health Medical Plan notified more than 238,000 members October 26 about a vendor-related data incident. A proposed class action accuses University Hospitals of negligence after an October 22 cyberattack that took its MyChart portal offline; the Cleveland patient's suit, filed October 28, claims more than a million records were exposed, a number University Hospitals has not confirmed. University of New Mexico Health Sciences Center disclosed a cyberattack October 26 that diverted ambulances for about two hours; the BYOD extortion group claims it compromised 36,000 systems, a figure UNM has not confirmed. Philips updated its Node2Shell advisory October 27 for CVE-2026-111497, the Node.js Brotli decoder flaw it first flagged October 26 against PIC iX 4.x; the advisory still names no impacted products or fixed version. Philips updated its PHP2Shell advisory October 27 for CVE-2026-109618 and CVE-2026-109619, adding five more affected products including IntelliSpace Portal V12 and Philips Axon to the seven already listed. NorthShore Health Centers disclosed a data breach to patients October 27, one of several Midwest provider notifications issued that week. Denver Health Medical Plan notified more than 238,000 members October 26 about a vendor-related data incident.

Vulnerability

Philips confirms researcher-reported vulnerabilities in the Xper-IM Connect system

MedDevice Cyber Staff · Jul 14 · 2 min read · Via Philips security disclosure

Philips published vulnerability information for the Xper-IM Connect system on July 14, 2016. Security researchers had contacted the company in the second quarter of 2016 about potential vulnerabilities in the product.

Philips said it handled the report under its Responsible Disclosure policy and worked with the researchers to address the identified vulnerabilities. Coordinated disclosure of this kind gives hospitals a manufacturer statement and a remediation path before the details circulate publicly. Sites running Xper-IM Connect should treat the Philips notice as the authoritative record of affected configurations.

Are you a representative of Philips? Submit an official response →

Remediation Desk

For ProvidersOperators, hospitals, and clinical engineering

Hospitals running Philips Xper-IM Connect should apply the remediation Philips published for the researcher-reported vulnerabilities. Until that is confirmed, keep the system on a restricted network segment.

Check the Philips notice. Read the July 14, 2016 Xper-IM Connect information and identify which installed systems it covers.
Apply the vendor remediation. Install the update or configuration change Philips specifies, through Philips service where required.
Restrict network access. Limit which hosts can reach Xper-IM Connect until the fix is confirmed on every system.

For Device ManufacturersFix the class in the product

The flaw is in the OS inside the controller, or a system past end of service still in the field. As the maker, own the embedded OS and server lifecycle as a safety obligation, design controllers to update in the field, and make every fault degrade to a defined safe state.

Own the OS lifecycle. Patch the OS and server components on a schedule with a tested delivery path.
Design for field update. And for planned replacement, so an unpatchable unit has a path off the network.
Degrade to safe. A fault drives a defined safe state, never an unexpected stop on a life-sustaining device.

Mapped EMB3D mitigations

Questions & Answers

Who reported vulnerabilities in the Philips Xper-IM Connect system?

Security researchers contacted Philips in the second quarter of 2016 about potential vulnerabilities in Xper-IM Connect, and Philips published vulnerability information on July 14, 2016.

How did Philips handle the 2016 Xper-IM Connect vulnerability report?

Philips said it followed its Responsible Disclosure policy and collaborated with the researchers to address the vulnerabilities in the Xper-IM Connect system, publishing information on July 14, 2016.

← Back to Vulnerabilities