Comparison Overview
Sunway Healthcare Group
Sunway Healthcare Group
5, Jalan Lagoon Selatan, Bandar Sunway, Petaling Jaya, 47500, MY
Last Update: 29/11/2025
Sunway Healthcare Group (SHG) is Asia's multi-award winning integrated private healthcare group with a network of hospitals and health services operating in Malaysia & Singapore serving patients from more than 170 countries worldwide since inception of the flagship Sunw...
Select Medical
4714 Gettysburg Rd, Mechanicsburg, 17055, US
Last Update: 01/04/2026
Select Medical made a commitment more than 20 years ago to deliver an exceptional patient care experience that promotes healing and recovery in a compassionate environment. We have honored that promise by helping define the nation's standard of excellence in specialized...
Compliance Ranges Comparison
Sunway Healthcare Group
Select Medical
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Sunway Healthcare Group in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Select Medical in 2026.
Incident History - Sunway Healthcare Group (X = Date, Y = Severity)
Sunway Healthcare Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Select Medical (X = Date, Y = Severity)
Select Medical cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Sunway Healthcare Group
Select Medical
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: *.*.