Comparison Overview
Philips

Philips
Amstelplein 2, Amsterdam, 1096 BC, NL
Last Update: 14/08/2026
Over the past decade we have transformed into a focused leader in health technology. At Philips, our purpose is to improve people’s health and well-being through meaningful innovation. We aim to improve 2.5 billion lives per year by 2030, including 400 million in under...

Memorial Hermann Health System
Houston, US
Last Update: 05/04/2026
Advancing Health. Personalizing Care. Memorial Hermann Health System is a nonprofit, values-driven, community-owned health system dedicated to improving health. A fully integrated health system with more than 260 care delivery sites throughout the Greater Houston area...
Compliance Ranges Comparison

Philips







Memorial Hermann Health System






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Philips has 111.27% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Memorial Hermann Health System in 2026.
Incident History - Philips (X = Date, Y = Severity)
Philips cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Memorial Hermann Health System (X = Date, Y = Severity)
Memorial Hermann Health System cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Philips

Memorial Hermann Health System
FAQ
Latest Global CVEs
Omni C20 lacks proper certificate validation which could allow an attacker to perform a man-in-the-middle attack which could allow them to execute arbitrary code.
Omni C20 uses hard-coded credentials that could allow an attacker to monitor log files to obtain credentials to access information like mapping data.
The affected products are vulnerable to command injection attack that could allow an unauthenticated attacker to execute system commands during the pairing process.
The Botslab G980H dash camera firmware contains an authentication vulnerability in the root account exposed through the device's UART interface. The affected account does not require a password before granting access to a privileged system interface, and the interface also displays the device's WiFi password during startup. An unauthenticated attacker with physical access to the device could connect to the UART interface, obtain root privileges, and recover the WiFi password.
The Botslab G980H dash camera firmware generates the default WiFi password using predictable device information, portions of which are advertised by the product. An unauthenticated attacker within WiFi range could potentially determine the remaining password characters through limited guessing and gain unauthorized access to the device network.