Comparison Overview
Amsterdam UMC

Amsterdam UMC
Meibergdreef 9, Amsterdam, undefined, 1100 DE, NL
Last Update: 05/03/2026
Hallo. Wij zijn Amsterdam UMC. De krachten van AMC en VUmc gebundeld. Samen bouwen we aan een samenleving waarin patiënten worden genezen en ziekten worden voorkomen, vooral wanneer de aandoening bijzonder is en de behandeling complex. Samen leiden we de beste artsen e...

UMC Utrecht
Heidelberglaan 100, Utrecht, Netherlands, 3508GA, NL
Last Update: 05/02/2026
Elke dag werken we allemaal aan het verder verbeteren van de zorg en de gezondheid van mensen. Vooraan staan is niet genoeg. We willen vooroplopen en de zorg in Nederland verder brengen. Met betrekking tot kennisinnovatie zetten we in op zes inhoudelijke speerpunten: •...
Compliance Ranges Comparison

Amsterdam UMC







UMC Utrecht






Benchmark & Cyber Underwriting Signals
Incidents vs Ziekenhuizen en gezondheidszorg Industry Avg (This Year)
No incidents recorded for Amsterdam UMC in 2026.
Incidents vs Ziekenhuizen en gezondheidszorg Industry Avg (This Year)
No incidents recorded for UMC Utrecht in 2026.
Incident History - Amsterdam UMC (X = Date, Y = Severity)
Amsterdam UMC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UMC Utrecht (X = Date, Y = Severity)
UMC Utrecht cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Amsterdam UMC

UMC Utrecht
FAQ
Latest Global CVEs
clash-verge-service-ipc before 2.3.0 has a world-reachable IPC endpoint, leading to local privilege escalation.
A vulnerability was identified in theonedev onedev up to 15.0.5. This vulnerability affects the function canAccessIssue of the file /issues/ of the component Pull Request Handler. Such manipulation of the argument issue leads to improper authorization. It is possible to launch the attack remotely. Upgrading to version 15.0.6 is able to resolve this issue. It is advisable to upgrade the affected component.
A vulnerability was determined in theonedev onedev up to 15.0.5. This affects an unknown part of the file /repositories/{projectId}/default-branch of the component REST API. This manipulation of the argument project.defaultBranch causes improper authorization. It is possible to initiate the attack remotely. Upgrading to version 15.0.6 is able to mitigate this issue. Upgrading the affected component is advised.
A vulnerability was found in theonedev onedev up to 15.0.5. Affected by this issue is some unknown functionality of the file /projects/ of the component Parent Project Handler. The manipulation of the argument project.parentId results in improper authorization. The attack may be performed from remote. Upgrading to version 15.0.6 can resolve this issue. It is recommended to upgrade the affected component.
A vulnerability has been found in theonedev onedev up to 15.0.5. Affected by this vulnerability is an unknown functionality of the file /projects. The manipulation of the argument project.forkedFromId leads to improper authorization. The attack is possible to be carried out remotely. Upgrading to version 15.0.6 addresses this issue. Upgrading the affected component is recommended.