Comparison Overview
Franciscan Physician Network

Franciscan Physician Network
Franciscan Alliance -, Mishawaka, US
Last Update: 02/04/2026
BRING YOUR PASSION TO FRANCISCAN PHYSICIAN NETWORK The time is right; Franciscan Physician Network is recruiting dynamic professionals like you. It takes more than just knowledge to be a part of our team. It takes caring, commitment and a strong passion for what ...

Rede D'Or
Rede D'Or São Luiz, Rio de Janeiro, BR
Last Update: 01/04/2026
A Rede D’Or é a maior rede de saúde da América Latina. São 79 hospitais e mais de 60 clínicas oncológicas com presença nos estados de AL, BA, CE, DF, MA, MG, MS, PA, PB, PE, PR, RJ, SE, SP. Referência em qualidade técnica, a Rede D’Or atua em serviços complementare...
Compliance Ranges Comparison

Franciscan Physician Network







Rede D'Or






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Franciscan Physician Network in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Rede D'Or in 2026.
Incident History - Franciscan Physician Network (X = Date, Y = Severity)
Franciscan Physician Network cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Rede D'Or (X = Date, Y = Severity)
Rede D'Or cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Franciscan Physician Network

Rede D'Or
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.