Comparison Overview
OYO Arabia

OYO Arabia
18th floor, Office 1802 The Exchange Tower Business Bay, Dubai, Dubai, 124743, AE
Last Update: 01/03/2026
Our goal is to change the way people stay away from home. We are the World's Fastest growing Hotel chain, offering standardised and hassle-free stay experiences at an unmatched price. We are now in the Middle east to help you find your perfect space in every place.

Radisson Hotel Group
44 Avenue du Bourget, Brussels, B-1130, BE
Last Update: 01/04/2026
Radisson Hotel Group is an international hotel group, operating in EMEA and APAC with over 1,320 hotels in operation and under development in +95 countries. The international hotel group is rapidly expanding with a plan to significantly grow the portfolio. The Group’s o...
Compliance Ranges Comparison

OYO Arabia







Radisson Hotel Group






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for OYO Arabia in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Radisson Hotel Group in 2026.
Incident History - OYO Arabia (X = Date, Y = Severity)
OYO Arabia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Radisson Hotel Group (X = Date, Y = Severity)
Radisson Hotel Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

OYO Arabia

Radisson Hotel Group
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.