Comparison Overview
AdventHealth Georgia
AdventHealth Georgia
None, None, Rome, Georgia, None, US, None
Last Update: 14/03/2026
We’re passionate about delivering the highest-quality care in the community we call home. And by joining the AdventHealth family, the care you know from the team you trust is only growing stronger. As part of the AdventHealth nationwide network, we’ll continue to elev...
Philips
Amstelplein 2, Amsterdam, 1096 BC, NL
Last Update: 05/04/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...
Compliance Ranges Comparison
AdventHealth Georgia
Philips
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for AdventHealth Georgia in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Philips has 7.41% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - AdventHealth Georgia (X = Date, Y = Severity)
AdventHealth Georgia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Philips (X = Date, Y = Severity)
Philips cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
AdventHealth Georgia
Philips
FAQ
Latest Global CVEs
Fides is an open-source privacy engineering platform. From version 2.33.0 to before version 2.84.5, there is a DOM-based XSS vulnerability in fides.js via the fides_description override. This issue has been patched in version 2.84.5.
WACRM prior to commit 73041bf contain an authorization bypass vulnerability in the automation engine that allows authenticated attackers to access and modify contacts belonging to other tenants by supplying an arbitrary caller-controlled contact_id in the POST request body without tenant ownership verification. Attackers can exploit the service-role client that bypasses row-level security to modify victim contact fields including name, email, and company across tenant boundaries using only a known contact UUID.
Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as valid end tags, allowing subsequent content to escape sanitization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
Headplane is a feature-complete Web UI for Headscale. Prior to versions 0.6.3 and 0.7.0-beta.3, Headplane was vulnerable to a path traversal / authorization bypass in the Headscale API client used by node and user rename operations. This issue has been patched in versions 0.6.3 and 0.7.0-beta.3.