Comparison Overview
UVA Imaging

UVA Imaging
415 Ray C. Hunt Drive, Charlottesville, Virginia, 22903, US
Last Update: 26/04/2026
Our mission is to provide each patient with quality, personalized care in a comfortable setting while offering referring physicians imaging services that accommodate their most specific needs. We combine the comfort and convenience of outpatient care with the expertise ...

Fairview Health Services
2450 Riverside Ave, Minneapolis, 55454, US
Last Update: 29/03/2026
Fairview Health Services is Minnesota’s choice for healthcare. We’re an industry-leading, award-winning, nonprofit offering a full network of healthcare services. Our broad network is designed to be ready for our patients’ every need, while delivering quality care with ...
Compliance Ranges Comparison

UVA Imaging







Fairview Health Services






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for UVA Imaging in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Fairview Health Services in 2026.
Incident History - UVA Imaging (X = Date, Y = Severity)
UVA Imaging cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Fairview Health Services (X = Date, Y = Severity)
Fairview Health Services cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

UVA Imaging

Fairview Health Services
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.