Comparison Overview
Memorial Health
Memorial Health
4700 Waters Ave, Savannah, Georgia, 31404, US
Last Update: 23/02/2026
Since becoming part of HCA Healthcare in 2018, Memorial Health has continued to make a positive impact in the 35+ counties it serves across southeast Georgia and southern South Carolina. In addition to Memorial Health University Medical Center, the Memorial Health netwo...
DaVita Kidney Care
2000 16th Street, Denver, 80202, US
Last Update: 24/04/2026
DaVita means “to give life,” reflecting our proud history as leaders in dialysis—an essential, life-sustaining treatment for those living with end stage kidney disease (ESKD). Today, our mission is to minimize the devastating impacts of kidney disease across the full sp...
Compliance Ranges Comparison
Memorial Health
DaVita Kidney Care
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Memorial Health in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
DaVita Kidney Care has 88.68% more incidents than the average of all companies with at least one recorded incident.
Incident History - Memorial Health (X = Date, Y = Severity)
Memorial Health cyber incidents detection timeline including parent company and subsidiaries.
Incident History - DaVita Kidney Care (X = Date, Y = Severity)
DaVita Kidney Care cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Memorial Health
DaVita Kidney Care
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: *.*.