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

Baxter Starling fluid monitor runs unsupported Windows Embedded Compact 7

MedDevice Cyber Staff · Jun 1 · 3 min read · Via Baxter Starling-2026-001 bulletin

Baxter published bulletin Starling-2026-001 in June 2026 on historical vulnerabilities in the Starling Fluid Management Monitoring System. A Baxter security assessment identified potential vulnerabilities, including use of the unsupported Windows Embedded Compact 7 operating system, which has had no vendor security patches since 2021.

Baxter says exploitation would typically require physical access to the device and/or access to exposed interfaces. Every OS flaw found since 2021 stays open on the platform, so the remaining controls are physical custody and what the device exposes.

An end-of-support OS turns every future OS flaw into a permanent finding. Manufacturers have to plan the platform migration before the OS vendor stops shipping fixes, because the device outlives the support window.

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

Remediation Desk

For ProvidersOperators, hospitals, and clinical engineering

Windows Embedded Compact 7 has received no vendor security patches since 2021, so OS-level flaws on Starling stay open. Hospitals should follow Baxter's Starling-2026-001 guidance, keep units physically controlled and limit access to exposed interfaces. Manufacturers should plan OS migration ahead of end of support.

Read Starling-2026-001. Apply the compensating controls Baxter lists in the bulletin for each Starling unit.
Control physical access. Keep Starling monitors in supervised areas and secure them when not in use.
Limit exposed interfaces. Restrict network and port access to the Starling system to what clinical use requires.
Plan OS lifecycle. Manufacturers should schedule platform migration before the embedded OS leaves vendor support.

For Device ManufacturersAm I affected, and how to fix the class

Am I affected?

This class applies to devices with the signals and properties below. Check them against your product to gauge exposure. The named product rows list what the sources state about the affected product.

Required

Named operating system

Starling Fluid Management Monitoring System

PID-23 Named operating system

Fix the class in your 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

What did Baxter disclose about the Starling Fluid Management Monitoring System?

Baxter's Starling-2026-001 bulletin, published in June 2026, says a security assessment found potential vulnerabilities in the Starling Fluid Management Monitoring System, including use of the unsupported Windows Embedded Compact 7 operating system, which has had no vendor security patches since 2021.

How could the Baxter Starling vulnerabilities be exploited?

Baxter's Starling-2026-001 bulletin says exploitation would typically require physical access to the Starling Fluid Management Monitoring System and/or access to its exposed interfaces.

← Back to Vulnerabilities