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 every product is unaffected, patched or mitigated for Log4j

MedDevice Cyber Staff · Dec 13 · 2 min read · Via Baxter Log4j bulletin

Baxter published a Log4j bulletin on December 13, 2021 and updated it on December 28, 2021. It describes the vulnerabilities in the Apache Java-based logging library as critical and says its team was evaluating Baxter's Java based products for impact.

As of the update, Baxter says all Baxter products are either not impacted, patched, or mitigations have been applied. The bulletin names no product, version or CVE, and it points Hillrom product questions to Hillrom's responsible disclosure page. Customers with a Java-based Baxter system should ask which of those three states it is in.

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

Remediation Desk

For ProvidersOperators, hospitals, and clinical engineering

Baxter states that every product is unaffected, patched or mitigated for Log4j; the bulletin does not say which. Confirm with Baxter the status of each Java-based Baxter system in the fleet and record whether a patch or a mitigation is in place.

Ask for per-product status. Request from Baxter product security whether each Java-based system you run was not impacted, patched or mitigated.
Verify patches are installed. Confirm any Baxter Log4j patch is actually applied on site.
Check Hillrom products separately. Use Hillrom's responsible disclosure page for Hillrom-branded equipment.

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

Off-the-shelf software

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 Log4j vulnerability?

Baxter's Log4j bulletin, published December 13, 2021 and updated December 28, 2021, says all Baxter products are either not impacted, patched, or mitigations have been applied. It names no specific product or version.

Where do I find Log4j information for Hillrom products after the Baxter bulletin?

Baxter's December 2021 Log4j bulletin points customers to Hillrom's responsible disclosures page for Hillrom products and to productsecurity@baxter.com for questions about Baxter products.

← Back to Vulnerabilities