Comparison Overview
iHarbor - University of Maryland Medical System Innovation Center
iHarbor - University of Maryland Medical System Innovation Center
250 W Pratt St, Baltimore, 21201, US
Last Update: 12/12/2025
iHarbor leads the way in reimagining health care – bringing to life solutions that enhance quality, elevate outcomes and optimize operations. As the innovation and incubation studio at the University of Maryland Medical System (UMMS), iHarbor ideates and purposefully bu...
Access Healthcare
4300 Alpha Rd, Dallas, 75244, US
Last Update: 02/04/2026
Established in 2011, Access Healthcare remains at the forefront of healthcare management, allowing providers to focus on what matters most – their patients. Our reputation is built on investing in and developing innovative technology allowing us to deliver custom soluti...
Compliance Ranges Comparison
iHarbor - University of Maryland Medical System Innovation Center
Access Healthcare
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for iHarbor - University of Maryland Medical System Innovation Center in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Access Healthcare in 2026.
Incident History - iHarbor - University of Maryland Medical System Innovation Center (X = Date, Y = Severity)
iHarbor - University of Maryland Medical System Innovation Center cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Access Healthcare (X = Date, Y = Severity)
Access Healthcare cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
iHarbor - University of Maryland Medical System Innovation Center
Access Healthcare
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.