Comparison Overview
Apollo: delivering our electronic health record
Apollo: delivering our electronic health record
London, GB
Last Update: 01/03/2026
Apollo is our name for an ambitious programme to introduce Epic (a leading electronic patient records system) across Guy’s and St Thomas’ and at King's College Hospital. Epic is due to launch on 5 October 2023. It will transform the way that we work by replacing our ...
Encompass Health
9001 Liberty Pkwy, Birmingham, 35242, US
Last Update: 01/04/2026
Encompass Health is the largest owner and operator of rehabilitation hospitals in the United States. With a national footprint that includes more than 170 hospitals in 39 states and Puerto Rico, the Company provides high-quality, compassionate rehabilitative care for pa...
Compliance Ranges Comparison
Apollo: delivering our electronic health record
Encompass Health
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Apollo: delivering our electronic health record in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Encompass Health in 2026.
Incident History - Apollo: delivering our electronic health record (X = Date, Y = Severity)
Apollo: delivering our electronic health record cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Encompass Health (X = Date, Y = Severity)
Encompass Health cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Apollo: delivering our electronic health record
Encompass Health
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: *.*.