Comparison Overview
Saint John's Cancer Institute (formerly John Wayne Cancer Institute) at Providence
Saint John's Cancer Institute (formerly John Wayne Cancer Institute) at Providence
2200 Santa Monica Blvd, Santa Monica, US
Last Update: 04/04/2026
Saint John's Cancer Institute (formerly John Wayne Cancer Institute) is a cancer research institute dedicated to the understanding, diagnosis, and innovative treatment of cancer in order to eliminate patient suffering and prolong survival. Through continual innovation...
UPMC
US Steel Tower, 600 Grant Street, Pittsburgh, PA, US, 15219
Last Update: 01/04/2026
UPMC is a world-renowned, nonprofit health care provider and insurer committed to delivering exceptional, people-centered care and community services. Headquartered in Pittsburgh and affiliated with the University of Pittsburgh Schools of the Health Sciences, UPMC is sh...
Compliance Ranges Comparison
Saint John's Cancer Institute (formerly John Wayne Cancer Institute) at Providence
UPMC
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Saint John's Cancer Institute (formerly John Wayne Cancer Institute) at Providence in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
UPMC has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Saint John's Cancer Institute (formerly John Wayne Cancer Institute) at Providence (X = Date, Y = Severity)
Saint John's Cancer Institute (formerly John Wayne Cancer Institute) at Providence cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UPMC (X = Date, Y = Severity)
UPMC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Saint John's Cancer Institute (formerly John Wayne Cancer Institute) at Providence
UPMC
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: *.*.