Comparison Overview
Anantara Hotels & Resorts
Anantara Hotels & Resorts
88 The PARQ Building, 12th Fl. Ratchadaphisek Road, Bangkok, 10110, TH
Last Update: 28/02/2026
Anantara. The word in Sanskrit means "without end" and evokes the freedom, movement and harmony that are the spirit of the Anantara experience and culture. Since the Anantara experience was born in 2001 in Thailand, operating within one of Asia Pacific’s largest li...
Accor
82 rue Henri Farman, Issy-les-Moulineaux, Paris Region, FR, 92130
Last Update: 14/06/2026
We are Accor We are more than 290,000 hospitality experts placing people at the heart of what we do, creating emotion for our guests, and nurturing passion for service and achievement beyond limits. Building on the strength of our teams and of our fully integrated ecos...
Compliance Ranges Comparison
Anantara Hotels & Resorts
Accor
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Anantara Hotels & Resorts in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Accor in 2026.
Incident History - Anantara Hotels & Resorts (X = Date, Y = Severity)
Anantara Hotels & Resorts cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Accor (X = Date, Y = Severity)
Accor cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Anantara Hotels & Resorts
Accor
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: *.*.