Comparison Overview
Work Health Solutions
Work Health Solutions
2101 Forest Ave, San Jose, 95128, US
Last Update: 29/03/2026
We’re redefining the occupational health space to deliver better programs and care for all. We create proactive, customized solutions to keep workspaces healthy, safe and productive, so employees can thrive and reach their full potential.
Mayo Clinic
200 First St. S.W., Rochester, Minnesota, US, 55905
Last Update: 08/06/2026
Mayo Clinic has expanded and changed in many ways, but our values remain true to the vision of our founders. Our primary value – The needs of the patient come first – guides our plans and decisions as we create the future of health care. Join us and you'll find a cultur...
Compliance Ranges Comparison
Work Health Solutions
Mayo Clinic
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Work Health Solutions in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Mayo Clinic has 88.68% more incidents than the average of all companies with at least one recorded incident.
Incident History - Work Health Solutions (X = Date, Y = Severity)
Work Health Solutions cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mayo Clinic (X = Date, Y = Severity)
Mayo Clinic cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Work Health Solutions
Mayo Clinic
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: *.*.