Comparison Overview
Motel One Group
Motel One Group
Tegernseer Landstraße 165, Munich, 81539, DE
Last Update: 03/04/2026
The Munich-based company was founded in 2000 and currently operates over 90 hotels in 12 countries. Motel One offers a unique combination of high-quality interiors, exclusive design, excellent service and outstanding city centre locations at attractive prices. As the ...
MGM Resorts International
840 Grier Drive, Las Vegas, 89119, US
Last Update: 20/05/2026
The resorts and casinos of MGM Resorts International™ are some of the most famous in the world. Our 28 destinations are renowned for their winning combination of quality entertainment, luxurious facilities, and exceptional customer service. We are actively expanding o...
Compliance Ranges Comparison
Motel One Group
MGM Resorts International
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Motel One Group in 2026.
Incidents vs Hospitality Industry Avg (This Year)
MGM Resorts International has 88.68% more incidents than the average of all companies with at least one recorded incident.
Incident History - Motel One Group (X = Date, Y = Severity)
Motel One Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - MGM Resorts International (X = Date, Y = Severity)
MGM Resorts International cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Motel One Group
MGM Resorts International
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: *.*.