Comparison Overview
OYO LIFE India

OYO LIFE India
Sector 69, Gurugram, Haryana, 122001, IN
Last Update: 04/12/2025
𝗡𝗼𝘄 𝗰𝗵𝗼𝗼𝘀𝗲 𝗢𝗬𝗢 𝗟𝗶𝗳𝗲 𝗳𝗼𝗿 𝘆𝗼𝘂𝗿 𝗹𝗼𝗻𝗴 𝘁𝗲𝗿𝗺 𝗿𝗲𝗻𝘁𝗮𝗹 𝗻𝗲𝗲𝗱𝘀 𝗢𝗬𝗢𝗟𝗶𝗳𝗲.𝗶𝗻 | +𝟵𝟭-𝟵𝟬𝟲𝟵𝟬𝟬𝟬𝟮𝟯𝟰 F𝘂𝗿𝗻𝗶𝘀𝗵𝗲𝗱 and sanitised spaces 𝗮𝘁 𝗶𝗱𝗲𝗮𝗹 𝗹𝗼𝗰𝗮𝘁𝗶𝗼𝗻𝘀 𝗮𝗰𝗿𝗼𝘀𝘀 𝗕𝗮𝗻𝗴𝗮𝗹𝗼𝗿𝗲, 𝗣𝘂𝗻𝗲, 𝗡𝗼𝗶...

Whitbread
Whitbread Court, Houghton Regis, Dunstable, LU5 5XE, GB
Last Update: 07/08/2026
Whitbread PLC is the owner of the UK’s favourite hotel chain, Premier Inn, as well as restaurant brands, Beefeater, Brewers Fayre, Table Table, Bar + Block and Cookhouse and Pub. Whitbread employs more than 35,000 people in more than 1,200 Premier Inn hotels and restau...
Compliance Ranges Comparison

OYO LIFE India







Whitbread






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

OYO LIFE India

Whitbread
FAQ
Latest Global CVEs
Redis contains a use-after-free vulnerability in the 'tlsProcessPendingData()' function, which handles the TLS pending-data list if Redis is configured with TLS support. A remote, unauthenticated attacker may be able to execute arbitrary commands with the privileges of the Redis server. Fixed in Redis 8.2.9, 8.4.6, 8.6.6, 8.8.2, and 8.10.1.
- https://github.com/redis/redis/commit/6d088c335d5c3ec49a6c28486140b498e70b7834
- https://github.com/v12-security/pocs/tree/main/redis/server_ssl
- https://raw.githubusercontent.com/redis/redis/8.10/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.2/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.4/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.6/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.8/00-RELEASENOTES
Unrestricted Upload of File with Dangerous Type in the product photo upload in Roskus Prospero Flow CRM before 5.16.0 allows an authenticated user holding the create product permission (routine Seller role) to execute arbitrary JavaScript in the application origin. The photo validation rule classifies the file only by its content (magic bytes) and rejects only a fixed list of PHP extensions, while ProductSaveController::save() names the stored file using the client-supplied extension and copies it into the public web root. A file that begins with an image header and carries an HTML extension passes validation, is stored under public/asset/upload/product/, and is served with a text/html content type, turning the upload into first-party stored script execution.
A flaw was found in gdk-pixbuf. When loading a specially crafted JPEG image containing chunked ICC profile markers, an error during ICC profile parsing can leave stale size metadata after the profile buffer is freed. A subsequent allocation in the same decode can cause an out-of-bounds write, potentially crashing the application. To exploit this flaw, an application using gdk-pixbuf must process the malicious JPEG image. Affected version >= 2.26.4
A relative path traversal issue in the zip extraction functionality in AWS diagram-as-code (awsdac) in versions 0.10 through 0.23 can allow a third party to write arbitrary files to the local filesystem via crafted zip entry names containing path traversal sequences. This could allow the third party to perform inappropriate actions in the diagram bundle. To remediate this issue, users should upgrade to the version 0.24 or later.
A weakness has been identified in RooCodeInc Roo-Code up to 3.51.1. Affected by this issue is the function ExecaTerminalProcess of the component README File Handler. Executing a manipulation can lead to code injection. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks. Multiple isses were reported to the vendor beforehand. They explain, that "they all apply to Roo Code, a project we no longer support - the repository was archived a while ago, and we don't encourage anyone to use it." This vulnerability only affects products that are no longer supported by the maintainer.