Comparison Overview
iHarbor - University of Maryland Medical System Innovation Center
iHarbor - University of Maryland Medical System Innovation Center
250 W Pratt St, Baltimore, 21201, US
Last Update: 12/12/2025
iHarbor leads the way in reimagining health care – bringing to life solutions that enhance quality, elevate outcomes and optimize operations. As the innovation and incubation studio at the University of Maryland Medical System (UMMS), iHarbor ideates and purposefully bu...
Stanford Health Care
500 Pasteur Dr, Palo Alto, California, US, 94304
Last Update: 01/04/2026
Stanford Health Care, with multiple facilities throughout the Bay Area, is internationally renowned for leading edge and coordinated care in cancer care, neurosciences, cardiovascular medicine, surgery, organ transplant, medicine specialties, and primary care. Throughou...
Compliance Ranges Comparison
iHarbor - University of Maryland Medical System Innovation Center
Stanford Health Care
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for iHarbor - University of Maryland Medical System Innovation Center in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Stanford Health Care in 2026.
Incident History - iHarbor - University of Maryland Medical System Innovation Center (X = Date, Y = Severity)
iHarbor - University of Maryland Medical System Innovation Center cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Stanford Health Care (X = Date, Y = Severity)
Stanford Health Care cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
iHarbor - University of Maryland Medical System Innovation Center
Stanford Health Care
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.