Comparison Overview
Sengkang General Hospital
Sengkang General Hospital
110 Sengkang East Way , Singapore, 544886, SG
Last Update: 02/04/2026
Sengkang General Hospital (SKH) forms a vital part of Singapore's master plan to provide quality and accessible care to better serve the healthcare needs in North-Eastern Singapore. Reflecting our mission of achieving better health together, SKH's team of doctors, nur...
EsSalud
120 Jirón Domingo Cueto, Jesús María, 15072, PE
Last Update: 31/03/2026
El Seguro Social de Salud, EsSalud, es un organismo público descentralizado, con personería jurídica de derecho público interno, adscrito al Sector Trabajo y Promoción Social. Tiene por finalidad dar cobertura a los asegurados y sus derechohabientes, a través del otorg...
Compliance Ranges Comparison
Sengkang General Hospital
EsSalud
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Sengkang General Hospital in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for EsSalud in 2026.
Incident History - Sengkang General Hospital (X = Date, Y = Severity)
Sengkang General Hospital cyber incidents detection timeline including parent company and subsidiaries.
Incident History - EsSalud (X = Date, Y = Severity)
EsSalud cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Sengkang General Hospital
EsSalud
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: *.*.