Comparison Overview
Waterbury Hospital
Waterbury Hospital
64 Robbins Street, Waterbury, 06708, US
Last Update: 01/04/2026
At Waterbury Hospital, we strive every day to make your visit here a great patient experience by providing you with excellent care by the most caring doctors, nurses and staff. Waterbury Hospital was recognized by U.S. News and World Report as one of the best Regional H...
Optum
11000 Optum Circle, Eden Prairie , MN, US, 55344
Last Update: 05/04/2026
At Optum, we take a bold approach to solving the challenges of healthcare. We call it Healthy Optumism — the realistic yet hopeful belief that when you’re grounded in real world needs, human connection and data-driven expertise, better is always possible. We use advance...
Compliance Ranges Comparison
Waterbury Hospital
Optum
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Waterbury Hospital in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Optum in 2026.
Incident History - Waterbury Hospital (X = Date, Y = Severity)
Waterbury Hospital cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Optum (X = Date, Y = Severity)
Optum cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Waterbury Hospital
Optum
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: *.*.