Comparison Overview
UZ Leuven

UZ Leuven
Herestraat 49, Leuven, 3000, BE
Last Update: 01/03/2026
Topreferent zijn in patiëntenzorg. Opleiding geven aan artsen. Baanbrekend wetenschappelijk onderzoek verrichten. Dat zijn de drie hoofdopdrachten van UZ Leuven. In België en Europa spelen we een toonaangevende rol die we willen behouden en verder uitbouwen. Daarvoor bu...

Kaiser Permanente
1 Kaiser Plaza, Oakland, 94612, US
Last Update: 04/04/2026
At the heart of health care, you’ll find Kaiser Permanente. As the nation’s leading not-for-profit, integrated health plan, we make a difference in the lives of members, patients, and communities across the country. With 39 hospitals and more than 734 locations in eig...
Compliance Ranges Comparison

UZ Leuven







Kaiser Permanente






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for UZ Leuven in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Kaiser Permanente has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - UZ Leuven (X = Date, Y = Severity)
UZ Leuven cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Kaiser Permanente (X = Date, Y = Severity)
Kaiser Permanente cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

UZ Leuven

Kaiser Permanente
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.