Comparison Overview
Oracle Health

Oracle Health
2300 Oracle Way, Austin, 78741, US
Last Update: 23/06/2026
Oracle Health strives to connect providers, patients, and public health and life sciences organizations by leveraging the power of data. We aim to create a human-centered healthcare experience for patients—and help physicians reclaim the joy of medicine. For more than ...

Algar Tech
Avenida Floriano Peixoto, Uberlândia, 38405-184, BR
Last Update: 02/04/2026
Somos a Algar Tech CX. Com 26 anos de mercado, atuamos como parceira de negócio para a transformação digital de grandes corporações. Nosso portfólio possui serviços de Relacionamento com o Cliente, que visam melhorar a experiência dos consumidores. Somos mais de 7 mil a...
Compliance Ranges Comparison

Oracle Health







Algar Tech






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Oracle Health has 32.89% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Algar Tech in 2026.
Incident History - Oracle Health (X = Date, Y = Severity)
Oracle Health cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Algar Tech (X = Date, Y = Severity)
Algar Tech cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Oracle Health

Algar Tech
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.