Comparison Overview
Bumrungrad International Hospital
Bumrungrad International Hospital
33 Sukhumvit 3 (Soi Nana Nua), Bangkok, 10110, TH
Last Update: 04/04/2026
Bumrungrad International Hospital stands as arguably the most impressive medical facility in the region. It has 55 specialty centers, an internationally certified lab and pharmacy, clinical research centers, advanced imaging facilities, and a 24-hour emergency care uni...
Sharp HealthCare
8695 Spectrum Center Blvd., San Diego, 92123, US
Last Update: 30/03/2026
Sharp HealthCare is a not-for-profit health care system based in San Diego, California, with four acute care hospitals, three specialty hospitals, three medical groups and a health plan. We provide medical services in virtually all fields of medicine, including primary ...
Compliance Ranges Comparison
Bumrungrad International Hospital
Sharp HealthCare
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Bumrungrad International Hospital in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Sharp HealthCare in 2026.
Incident History - Bumrungrad International Hospital (X = Date, Y = Severity)
Bumrungrad International Hospital cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sharp HealthCare (X = Date, Y = Severity)
Sharp HealthCare cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Bumrungrad International Hospital
Sharp HealthCare
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: *.*.