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 says no products use a Bluetooth version affected by SweynTooth

MedDevice Cyber Staff · Mar 9 · 2 min read · Via Baxter SweynTooth bulletin

Baxter published a bulletin on March 9, 2020 on SweynTooth, the Bluetooth Low Energy vulnerabilities disclosed by researchers from the Singapore University of Technology and Design. The researchers disclosed 12 vulnerabilities in the software development kits of several BLE system-on-chip makers, and CISA published ICS alert ICS-ALERT-20-063-01 on March 3, 2020.

The flaws sit in specific BLE SoC implementations. They can allow an attacker in radio range to trigger deadlocks, crashes, buffer overflows, or the complete bypass of security. Baxter says its initial assessment found that no Baxter products use an impacted version of Bluetooth, and it will update the bulletin if necessary.

SweynTooth lives in chip vendor SDKs, so the real answer depends on knowing which SoC and SDK build each wireless product ships with.

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

Remediation Desk

For ProvidersOperators, hospitals, and clinical engineering

Baxter reports that no product uses an affected Bluetooth version, so there is no Baxter fix to apply for SweynTooth. Operators should confirm the BLE chipsets in other vendors' wireless devices against ICS-ALERT-20-063-01.

Record the Baxter finding. Mark Baxter products as not affected by SweynTooth in the device risk register.
Inventory BLE chipsets. Ask other suppliers which BLE SoC and SDK version their wireless devices use.
Watch the bulletin. 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

Wireless connectivity

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 devices vulnerable to SweynTooth?

No. Baxter's March 9, 2020 bulletin says an initial assessment found no Baxter products use an impacted version of Bluetooth for the SweynTooth BLE vulnerabilities in CISA alert ICS-ALERT-20-063-01.

What can an attacker do with the SweynTooth Bluetooth Low Energy flaws?

As Baxter's March 9, 2020 bulletin describes them, the SweynTooth flaws in BLE system-on-chip implementations allow an attacker in radio range to trigger deadlocks, crashes, buffer overflows, or the complete bypass of security.

← Back to Vulnerabilities