Comparison Overview
Landry's Seafood

Landry's Seafood
1510 West Loop South, Houston, Texas, 77027, US
Last Update: 07/03/2026
For more than six decades, the Landry's Seafood story has been a tale of legendary Gulf Coast cuisine and true hospitality. From the time the doors opened in 1947 at the first location in Lafayette, Louisiana, out of a family's home, to the present day, Landry's Seafood...

Radisson Hotel Group
44 Avenue du Bourget, Brussels, B-1130, BE
Last Update: 15/09/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

Landry's Seafood







Radisson Hotel Group






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Landry's Seafood in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Radisson Hotel Group in 2026.
Incident History - Landry's Seafood (X = Date, Y = Severity)
Landry's Seafood 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

Landry's Seafood

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