Comparison Overview
The Kerry Hotels
The Kerry Hotels
Kerry Centre, 683 King’s Road. Quarry Bay, Hong Kong, HK
Last Update: 22/04/2026
Guests are increasingly searching for more down-to-earth, less “big-box” experiences that offer a real sense of place and the neighborhood they are in. With the belief that a hotel needs to feel like a part of the community that it’s in, the first Kerry Hotels in the Sh...
Landry's
1510 West Loop South, Houston, 77027, US
Last Update: 01/04/2026
Landry's is a multinational, diversified restaurant, hospitality, gaming, and entertainment leader based in Houston, Texas. The company operates more than 600 establishments around the world, including well-known concepts, such as Landry’s Seafood House, Bubba Gump S...
Compliance Ranges Comparison
The Kerry Hotels
Landry's
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for The Kerry Hotels in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Landry's in 2026.
Incident History - The Kerry Hotels (X = Date, Y = Severity)
The Kerry Hotels cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Landry's (X = Date, Y = Severity)
Landry's cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
The Kerry Hotels
Landry's
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.