Comparison Overview
Labcorp
Labcorp
531 South Spring Street, Burlington, 27215, US
Last Update: 25/09/2026
Clear and confident health care decisions begin with questions. At Labcorp, we’re constantly in pursuit of answers. As a global leader of innovative and comprehensive laboratory services, we help doctors, hospitals, pharmaceutical companies, researchers and patients m...
IHH Healthcare
Level 11 Block A, Pantai Hospital Kuala Lumpur, 8 Jalan Bukit Pantai, Kuala Lumpur, MY, 59100
Last Update: 17/09/2026
A world-leading multinational healthcare provider, IHH believes that making a difference starts with our aspiration to Care. For Good. Our team of 70,000 people commit to deliver greater good to our patients, people, the public and our planet, as we live our purpose ...
Compliance Ranges Comparison
Labcorp
IHH Healthcare
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Labcorp has 29.08% fewer 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 IHH Healthcare in 2026.
Incident History - Labcorp (X = Date, Y = Severity)
Labcorp cyber incidents detection timeline including parent company and subsidiaries.
Incident History - IHH Healthcare (X = Date, Y = Severity)
IHH Healthcare cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Labcorp
IHH Healthcare
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.