Comparison Overview
Helios Kliniken GmbH
Helios Kliniken GmbH
Friedrichstraße 136, Berlin, 10117, DE
Last Update: 26/04/2026
Willkommen bei Europas führendem privaten Krankenhausbetreiber. In Deutschland verfügt Helios über mehr als 80 Kliniken, rund 220 Medizinische Versorgungszentren (MVZ) mit etwa 570 kassenärztlichen Sitzen, sechs Präventionszentren und 27 arbeitsmedizinische Zentren. Jä...
UnityPoint Health
1776 West Lakes Parkway,, West Des Moines, 50266, US
Last Update: 02/04/2026
As an integrated health system, we provide care throughout Iowa, western Illinois and southern Wisconsin in not-for-profit hospitals, clinics and home health settings. Each year, we serve nearly 8 million patient visits of all different types, including around 100,000 s...
Compliance Ranges Comparison
Helios Kliniken GmbH
UnityPoint Health
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Helios Kliniken GmbH in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for UnityPoint Health in 2026.
Incident History - Helios Kliniken GmbH (X = Date, Y = Severity)
Helios Kliniken GmbH cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UnityPoint Health (X = Date, Y = Severity)
UnityPoint Health cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Helios Kliniken GmbH
UnityPoint 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: *.*.