Comparison Overview
Wyndham Hotels & Resorts EMEA
Wyndham Hotels & Resorts EMEA
3 Shortlands, London, W6 8DA, GB
Last Update: 03/04/2026
We are Wyndham Hotels & Resorts, the world’s largest hotel franchising company. Our 25 globally recognized brands, spanning 8,300 hotels and 100+ countries, uniquely position us to serve owners and travelers of virtually every type, everywhere. • We have a brand for ev...
Hyatt
150 N Riverside Plaza, Chicago, IL, US, 60606
Last Update: 20/05/2026
Hyatt is guided by its purpose: to care for people so they can be their best. Hyatt’s portfolio includes 1,000+ hotel and all-inclusive properties in over 75 countries across 6 continents. Hyatt’s offerings include brands in the Timeless Collection, including Park Hyatt...
Compliance Ranges Comparison
Wyndham Hotels & Resorts EMEA
Hyatt
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Wyndham Hotels & Resorts EMEA in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Hyatt in 2026.
Incident History - Wyndham Hotels & Resorts EMEA (X = Date, Y = Severity)
Wyndham Hotels & Resorts EMEA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hyatt (X = Date, Y = Severity)
Hyatt cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Wyndham Hotels & Resorts EMEA
Hyatt
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: *.*.