Comparison Overview
Miraval The Red Sea

Miraval The Red Sea
Shura Island, SA
Last Update: 28/12/2025
Coming soon: Miraval The Red Sea, where life serenely balances between desert and sea through personal discovery and quiet reflection.

Hyatt
150 N Riverside Plaza, Chicago, 60606, US
Last Update: 03/10/2026
Hyatt Hotels Corporation, headquartered in Chicago, is a leading global hospitality company guided by its purpose – to care for people so they can be their best. As of December 31, 2025, the Company's portfolio included more than 1,500 hotels and all-inclusive propertie...
Compliance Ranges Comparison

Miraval The Red Sea







Hyatt






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Miraval The Red Sea in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Hyatt in 2026.
Incident History - Miraval The Red Sea (X = Date, Y = Severity)
Miraval The Red Sea cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hyatt (X = Date, Y = Severity)
Hyatt cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Miraval The Red Sea

Hyatt
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.