Comparison Overview
Hôtel du Léman
Hôtel du Léman
Chemin de la Fontaine 2, Jongny, 1805, CH
Last Update: 05/03/2026
Hôtel du Léman is a small and friendly establishment where we take the time to get to know our guests. You’ll feel completely at home. Around the leafy gardens, in the relaxation area equipped with teak loungers or beside the pétanque court, enjoy the positive energy th...
Hilton Grand Vacations
5323 Millenia Lakes Boulevard, Orlando, 32839, US
Last Update: 03/04/2026
Hilton Grand Vacations is a global leader in vacation ownership, developing, marketing and operating a portfolio of high-quality, shared-ownership properties in highly desired vacation destinations. Our company also manages and operates innovative club membership progra...
Compliance Ranges Comparison
Hôtel du Léman
Hilton Grand Vacations
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Hôtel du Léman in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Hilton Grand Vacations in 2026.
Incident History - Hôtel du Léman (X = Date, Y = Severity)
Hôtel du Léman cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hilton Grand Vacations (X = Date, Y = Severity)
Hilton Grand Vacations cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Hôtel du Léman
Hilton Grand Vacations
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: *.*.