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...
University Hospitals
University Hospitals, Cleveland, 44106, US
Last Update: 03/04/2026
Founded in 1866, University Hospitals serves the needs of patients through an integrated network of 23 hospitals (including 5 joint ventures), more than 50 health centers and outpatient facilities, and over 200 physician offices in 16 counties throughout northern Ohio. ...
Compliance Ranges Comparison
UZ Leuven
University Hospitals
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)
No incidents recorded for University Hospitals in 2026.
Incident History - UZ Leuven (X = Date, Y = Severity)
UZ Leuven cyber incidents detection timeline including parent company and subsidiaries.
Incident History - University Hospitals (X = Date, Y = Severity)
University Hospitals cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
UZ Leuven
University Hospitals
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.