Comparison Overview
Medcurity
Medcurity
157 S Howard St, Spokane, 99201, US
Last Update: 21/05/2026
Healthcare compliance is complicated. We're here to help. Our AI-powered tool simplifies your HIPAA Risk Analysis, so you can leave behind the clunky, confusing spreadsheets for good. Our team has many years of experience in healthcare and technology. The founders prev...
Helios Health GmbH
Friedrichstrasse 136, Berlin, 10117, DE
Last Update: 02/04/2026
Based on our extensive expertise and know how we seek to ensure high quality, efficient and patient focused healthcare, locally as well as within an international environment. For this purpose Helios Health was founded in 2017. Helios Health combines Helios Germany (He...
Compliance Ranges Comparison
Medcurity
Helios Health GmbH
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Medcurity has 29.58% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Helios Health GmbH in 2026.
Incident History - Medcurity (X = Date, Y = Severity)
Medcurity cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Helios Health GmbH (X = Date, Y = Severity)
Helios Health GmbH cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Medcurity
Helios Health GmbH
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: *.*.