Comparison Overview
Open Medical
Open Medical
Floor 7, 97-107 Uxbridge Rd, London, W5 5TL, GB
Last Update: 26/06/2026
We are a team of clinician-led digital health experts delivering award-winning, cloud-based software for healthcare organisations, powered by our Pathpoint® platform. Our solutions streamline clinical and operational workflows from referral to discharge, across various ...
UCHealth
12401 E. 17th Avenue, Aurora, 80045, US
Last Update: 01/04/2026
At UCHealth, we do things differently. We strive to promote individual and community health and leave no question unanswered along the way. We’re driven to improve and optimize health care. Our network of nationally-recognized hospitals, clinic locations and health car...
Compliance Ranges Comparison
Open Medical
UCHealth
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Open Medical has 29.58% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for UCHealth in 2026.
Incident History - Open Medical (X = Date, Y = Severity)
Open Medical cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UCHealth (X = Date, Y = Severity)
UCHealth cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Open Medical
UCHealth
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: *.*.