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

bioMérieux lists VITEK 2, VIDAS 3 and BACT/ALERT 3D among products clear of Log4j

MedDevice Cyber Staff · Jan 26 · 2 min read · Via bioMérieux security advisories

bioMérieux updated its Apache Log4j advisory on January 26, 2022 with products and product features it found are not running the impacted versions of Log4j disclosed as of that date. The list includes VITEK 2 8.x and below, VIDAS 3 1.3 and below, BACT/ALERT 3D, BIOFIRE FILMARRAY 2.0 and TORCH, MYLA Lab Analytics CLOUD 1.2 and the COPAN WASP.

The investigation was still open. bioMérieux said it was determining whether other products or product features run affected versions, including in its BioFire franchise, and would make remediation available as soon as possible. In the meantime it recommended isolating medical systems on a dedicated LAN or VLAN and never exposing medical devices directly to the internet.

A not-affected list tied to a disclosure cutoff answers only for the products on it. Anything missing from the list stays unknown until the vendor updates it.

Are you a representative of a manufacturer named here? Submit an official response →

Remediation Desk

For ProvidersOperators, hospitals, and clinical engineering

bioMérieux's January 26, 2022 Log4j update lists products not running impacted Log4j versions, including VITEK 2 8.x and below and VIDAS 3 1.3 and below. Products not on the list were still under investigation, with no fix published. Isolate bioMérieux systems on a dedicated network segment and confirm status for anything missing from the list.

Check the list. Match installed bioMérieux products and versions against the January 26, 2022 not-affected list.
Chase the gaps. Ask bioMérieux for Log4j status on any installed product missing from the list.
Isolate the systems. Put bioMérieux systems on a dedicated LAN or VLAN with no direct internet exposure.

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.

Required

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

Is bioMérieux VITEK 2 affected by the Log4j vulnerabilities?

bioMérieux said on January 26, 2022 that VITEK 2 8.x and below is not running the impacted versions of Log4j disclosed as of that date.

What did bioMérieux recommend while its Log4j investigation continued?

In its January 26, 2022 Log4j advisory, bioMérieux recommended isolating medical systems on a dedicated LAN or VLAN and never exposing medical devices directly to the internet.

← Back to Vulnerabilities