Comparison Overview
Fresenius Group
Fresenius Group
Else-Kröner-Straße 1, Bad Homburg, 61352, DE
Last Update: 04/07/2026
Committed to Life - We save and improve human lives with affordable, accessible, and innovative healthcare products and the highest quality in clinical care. Fresenius is a global healthcare company headquartered in Bad Homburg v. d. Höhe, Germany. In fiscal year 2024,...
Northwestern Medicine
251 E Huron St, Chicago, 60611, US
Last Update: 18/05/2026
Northwestern Medicine is the collaboration between Northwestern Memorial HealthCare and Northwestern University Feinberg School of Medicine around a strategic vision to transform the future of health care. It encompasses the research, teaching, and patient care activiti...
Compliance Ranges Comparison
Fresenius Group
Northwestern Medicine
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Fresenius Group in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Northwestern Medicine in 2026.
Incident History - Fresenius Group (X = Date, Y = Severity)
Fresenius Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Northwestern Medicine (X = Date, Y = Severity)
Northwestern Medicine cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Fresenius Group
Northwestern Medicine
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: *.*.