Comparison Overview
Erasmus MC
Erasmus MC
Dr. Molewaterplein 40, Rotterdam, Zuid-Holland, NL, 3015 GD
Last Update: 03/04/2026
We are Erasmus MC. Our roots lie in Rotterdam, a city and port of international standing. We are the most innovative university medical center in the Netherlands and one of the world’s leading centers of scientific research. We are committed to achieving a healthy popul...
University of Maryland Medical System
22 S. Greene St, Baltimore, 21201, US
Last Update: 02/04/2026
The University of Maryland Medical System (UMMS) was created in 1984 when the state-owned University Hospital became a private, nonprofit organization. It has evolved into a multi-hospital system with academic, community and specialty service missions reaching every par...
Compliance Ranges Comparison
Erasmus MC
University of Maryland Medical System
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Erasmus MC in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for University of Maryland Medical System in 2026.
Incident History - Erasmus MC (X = Date, Y = Severity)
Erasmus MC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - University of Maryland Medical System (X = Date, Y = Severity)
University of Maryland Medical System cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Erasmus MC
University of Maryland Medical System
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.