Comparison Overview
Fairmont Monte Carlo
Fairmont Monte Carlo
12 Avenue des Spélugues, Monte Carlo, undefined, 98000, MC
Last Update: 05/12/2025
The Fairmont Monte Carlo is a unique hotel located in the heart of the Principality of Monaco between the Mediterranean Sea and the famous hairpin turn of the Grand Prix Formula 1. Inaugurated in 1975 by Princess Grace Kelly, the Fairmont Monte Carlo offers an exclusiv...
Marriott Hotels
10400 Fernwood Rd, Bethesda, 20817, US
Last Update: 04/04/2026
With over 500 properties worldwide, Marriott Hotels has reimagined hospitality to exceed the expectations of business, group, and leisure travelers. Marriott Hotels, Marriott’s flagship brand of quality-tier, full-service hotels and resorts, provides consistent, de...
Compliance Ranges Comparison
Fairmont Monte Carlo
Marriott Hotels
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Fairmont Monte Carlo in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Marriott Hotels in 2026.
Incident History - Fairmont Monte Carlo (X = Date, Y = Severity)
Fairmont Monte Carlo cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Marriott Hotels (X = Date, Y = Severity)
Marriott Hotels cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Fairmont Monte Carlo
Marriott Hotels
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: *.*.