Comparison Overview
Royal Caribbean Group

Royal Caribbean Group
Royal Caribbean Group 1050 Caribbean Way Miami, Miami, Florida, US, 2312
Last Update: 17/09/2026
At Royal Caribbean Group, we deliver unforgettable vacations to guests who trust us with life’s greatest moments. We build the best ships, and even better careers, all while doing the right thing. We are passionate. We are innovative. We are unstoppable. We open the wor...

BCD Travel
Europalaan 300, Utrecht, NL, 3526 KS
Last Update: 15/10/2026
BCD Travel helps companies travel smart and achieve more. We drive program adoption, cost savings and talent retention through digital experiences that simplify business travel. Our 15,000+ dedicated team members service clients in 170+ countries as we shape a sustainab...
Compliance Ranges Comparison

Royal Caribbean Group







BCD Travel






Benchmark & Cyber Underwriting Signals
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for Royal Caribbean Group in 2026.
Incidents vs Travel Arrangements Industry Avg (This Year)
BCD Travel has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Royal Caribbean Group (X = Date, Y = Severity)
Royal Caribbean Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BCD Travel (X = Date, Y = Severity)
BCD Travel cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Royal Caribbean Group

BCD Travel
FAQ
Latest Global CVEs
A flaw was found in nfs-utils. An unauthenticated remote attacker can trigger a Denial of Service (DoS) by sending repeated state notification requests to an exposed rpc.statd service. The service fails to properly release memory allocated during callback processing, leading to continuous memory growth. Sustained requests can exhaust system resources, eventually causing the service to degrade or crash.
A flaw was found in parted. A heap-based buffer overflow exists in libparted's file system resizing logic when handling FAT16 volumes. By convincing a user or administrator to resize a specially crafted FAT16 file system image with malformed directory metadata, an attacker can trigger an oversized read into a fixed-size memory buffer. This issue causes memory corruption, resulting in an application crash and a denial of service (DoS).
A flaw was found in parted. A heap-based buffer overflow can occur when processing a specially crafted FAT32 filesystem due to an integer calculation error during buffer allocation. A local attacker could exploit this by enticing a user or automated service to open a malicious filesystem image, resulting in an application crash leading to a Denial of Service (DoS) or potential memory corruption.
A flaw was found in libarchive. An attacker can cause a Denial of Service (DoS) or potential information disclosure due to a use-after-free vulnerability, which occurs when a program reads memory that has already been released. This issue arises when the archive_entry_copy_mac_metadata() function deallocates an internal buffer before completing a data copy. An attacker who can supply input to an application utilizing this function can trigger the flaw to crash the application or read uninitialized memory data.
A flaw was found in Nautilus. When a removable drive or disk image is unmounted or ejected, Nautilus prompts the user to empty the trash without verifying whether the trash directory paths are symbolic links. An attacker can exploit this flaw by tricking a user into mounting a crafted storage volume and confirming the prompt to empty the trash, leading to the arbitrary deletion of files accessible to that user.