Comparison Overview
Hapag-Lloyd Cruises

Hapag-Lloyd Cruises
Heidenkamspweg 58, Hamburg, 20097, DE
Last Update: 23/01/2026
Hapag-Lloyd Cruises gilt im deutschsprachigen Raum als führende Kreuzfahrtmarke im Luxus- und Expeditionsbereich. Zur Flotte gehören aktuell fünf Schiffe. Unsere Schiffe sind klein, individuell und herausragend in ihrer Klasse: Die weltweit besten Luxusschiffe EUROPA u...

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...
Compliance Ranges Comparison

Hapag-Lloyd Cruises







Royal Caribbean Group






Benchmark & Cyber Underwriting Signals
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for Hapag-Lloyd Cruises in 2026.
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for Royal Caribbean Group in 2026.
Incident History - Hapag-Lloyd Cruises (X = Date, Y = Severity)
Hapag-Lloyd Cruises cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Royal Caribbean Group (X = Date, Y = Severity)
Royal Caribbean Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Hapag-Lloyd Cruises

Royal Caribbean Group
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.