Comparison Overview
Cencora
Cencora
N/A
Last Update: 07/10/2026
Cencora, a company building on the legacy of AmerisourceBergen, is a leading global pharmaceutical solutions organization centered on improving the lives of people and animals around the world. We connect manufacturers, providers, and patients to ensure that anyone can ...
UW Health
600 Highland Ave, Madison, 53792, US
Last Update: 05/09/2026
UW Health is an integrated academic health system that is home to the No. 1 hospital in Wisconsin (for the 14th year in a row) as ranked by U.S. News & World Report. We’re made up of six main hospitals, one JOA partner hospital in Madison and two hospitals located withi...
Compliance Ranges Comparison
Cencora
UW Health
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Cencora in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for UW Health in 2026.
Incident History - Cencora (X = Date, Y = Severity)
Cencora cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UW Health (X = Date, Y = Severity)
UW Health cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Cencora
UW Health
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.