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 finds no products using the IPnet TCP/IP stack behind Urgent/11

MedDevice Cyber Staff · Sep 24 · 2 min read · Via Baxter Urgent/11 bulletin

Baxter posted a bulletin on September 24, 2019 on Urgent/11, the 11 vulnerabilities (CVE-2019-12255 through CVE-2019-12265) that Wind River and Armis researchers reported in the Interpeak IPnet TCP/IP stack used in some versions of VxWorks. It cites ICS advisory ICSA-19-211-01 and medical advisory ICSMA-19-274-01 and notes the flaws were classified as critical, high and medium.

Baxter says an initial assessment found that no Baxter products use the IPnet TCP/IP stack or an impacted version of an RTOS. It updated the bulletin on October 21, 2019. Answering that cleanly takes a component inventory that goes down to the network stack of each embedded product.

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

Remediation Desk

For ProvidersOperators, hospitals, and clinical engineering

Baxter reports that none of its products use the IPnet stack or an affected RTOS, so no Baxter patch exists or is needed for Urgent/11. Operators should still check other vendors' VxWorks-based equipment against ICSMA-19-274-01.

Record the Baxter finding. Mark Baxter products as not affected by CVE-2019-12255 through CVE-2019-12265 in the vulnerability register.
Check other embedded devices. Ask other suppliers whether their products run VxWorks with the IPnet stack.
Watch for bulletin updates. Baxter says it will update the bulletin if necessary.

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.

Contributing

Wired network

Fix the class in your product

The advisory is not for a bug you wrote; it is in a component you embed. As the maker, pin dependencies to fixed versions, generate an SBOM on every build including transitive components, and gate the pipeline on known-vulnerable components so an advisory maps to your products automatically.

Pin and inventory. Exact versions, and a CycloneDX or SPDX SBOM as a build artifact including transitive deps.
Gate on advisories. A CI scan fails a release carrying a component with a known advisory.
Own the field patch path. Know how you deliver a dependency or platform patch to fielded devices before you need it.

Mapped EMB3D mitigations

Questions & Answers

Are Baxter products affected by the Urgent/11 VxWorks vulnerabilities?

No. Baxter's September 24, 2019 bulletin says an initial assessment found no Baxter products use the Interpeak IPnet TCP/IP stack or an impacted version of an RTOS, so Urgent/11 (CVE-2019-12255 through CVE-2019-12265) does not apply.

What is Urgent/11?

Urgent/11 is a set of 11 vulnerabilities, CVE-2019-12255 through CVE-2019-12265, reported by Wind River and Armis researchers in the Interpeak IPnet TCP/IP stack used in some versions of the VxWorks real time operating system.

← Back to Vulnerabilities