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 SureSigns VS4 monitors can be pushed into sending patient data to a remote destination

MedDevice Cyber Staff · Aug 20 · 2 min read · Via CISA ICSMA-20-233-01

CISA published advisory ICSMA-20-233-01 on August 20, 2020, covering Philips SureSigns VS4 vital signs monitors at version A.07.107 and prior. Cleveland Clinic reported the issue. The CSAF record lists one CVE, CVE-2020-16237, an improper input validation flaw (CWE-20) scored CVSS v3 2.1 with a physical attack vector.

The score understates the reach described in the risk evaluation: access to administrative controls and system configurations, including configuration changes that send patient data to a remote destination.

Philips did not release a patch. It recommends changing all system passwords on each VS4 to unique values, securing the device when not in use, and considering replacement of the VS4 with newer technology. Upgrade questions go to Philips service at 1-800-722-9377.

A vendor recommending replacement is telling you the product's security roadmap has ended, and the asset register should record that date.

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

Remediation Desk

For ProvidersOperators, hospitals, and clinical engineering

No patch is available for the SureSigns VS4. Set unique system passwords on every unit, physically secure monitors when not in use, and plan replacement with newer technology as Philips recommends.

Set unique passwords per device. Change every system password on each VS4 to a value used nowhere else, per the Installation and Configuration Guide.
Secure idle units. Store monitors where unauthorized people cannot reach their controls.
Check data destinations. Review each unit's configuration for any unexpected remote destination for patient data.
Budget for replacement. Add the VS4 to the replacement plan, since Philips recommends newer technology.

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

User accounts

Contributing

Handles patient data Hospital network

SureSigns VS4

PID-3321 User accounts Handles patient data

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 is CVE-2020-16237 in the Philips SureSigns VS4?

CVE-2020-16237 is an improper input validation flaw (CWE-20, CVSS v3 2.1) in Philips SureSigns VS4 version A.07.107 and prior. CISA advisory ICSMA-20-233-01, published August 20, 2020, says exploitation could give access to administrative controls and configuration that could send patient data to a remote destination.

Is there a patch for the Philips SureSigns VS4 vulnerability?

No patch is listed in CISA advisory ICSMA-20-233-01 from August 20, 2020. Philips recommends unique system passwords on each SureSigns VS4, securing the device when not in use, and considering replacement with newer technology.

← Back to Vulnerabilities