Comparison Overview
Aurora Medical Center - Burlington

Aurora Medical Center - Burlington
252 McHenry St, Burlington, 53105, US
Last Update: 01/03/2026
At the Aurora Medical Center – Burlington (formally Aurora Memorial Hospital of Burlington), we are committed to providing compassionate, quality care and innovative services to the Burlington community. Thank you for participating and engaging with Aurora Health Care ...

Sharp HealthCare
8695 Spectrum Center Blvd., San Diego, 92123, US
Last Update: 30/03/2026
Sharp HealthCare is a not-for-profit health care system based in San Diego, California, with four acute care hospitals, three specialty hospitals, three medical groups and a health plan. We provide medical services in virtually all fields of medicine, including primary ...
Compliance Ranges Comparison

Aurora Medical Center - Burlington







Sharp HealthCare






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Aurora Medical Center - Burlington in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Sharp HealthCare in 2026.
Incident History - Aurora Medical Center - Burlington (X = Date, Y = Severity)
Aurora Medical Center - Burlington cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sharp HealthCare (X = Date, Y = Severity)
Sharp HealthCare cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Aurora Medical Center - Burlington

Sharp HealthCare
FAQ
Latest Global CVEs
Use after free in Aura in Google Chrome prior to 150.0.7871.128 allowed a local attacker to potentially exploit heap corruption via a malicious file. (Chromium security severity: High)
Use after free in Ozone in Google Chrome on Linux prior to 150.0.7871.128 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
Out of bounds read and write in V8 in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Use after free in Cast in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Use after free in Network in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)