Comparison Overview
UPMC Supplier Opportunity & Inclusion
UPMC Supplier Opportunity & Inclusion
600 Grant St, US Steel Tower, Floor 59, Pittsburgh, Pennsylvania, US, 15219
Last Update: 16/03/2026
UPMC’s Supplier Opportunity and Inclusion Program, which began in 1989, and re-engineered in 2006, is designed to provide certified minority, woman-owned, LGTBE, Veteran, small, small disadvantaged, and HUBZone owned vendors equal access to procurement opportunities. Th...
Intermountain Health
5245 South College Drive, Murray , UT, US, 84123
Last Update: 02/04/2026
Headquartered in Utah with locations in six primary states and additional operations across the western U.S., Intermountain Health is a nonprofit system of 34 hospitals, 400+ clinics, a medical group of more than 4,800 employed physicians and advanced care providers, a ...
Compliance Ranges Comparison
UPMC Supplier Opportunity & Inclusion
Intermountain Health
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for UPMC Supplier Opportunity & Inclusion in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Intermountain Health in 2026.
Incident History - UPMC Supplier Opportunity & Inclusion (X = Date, Y = Severity)
UPMC Supplier Opportunity & Inclusion cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Intermountain Health (X = Date, Y = Severity)
Intermountain Health cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
UPMC Supplier Opportunity & Inclusion
Intermountain Health
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: *.*.