Comparison Overview
Best Western Hotels & Resorts
Best Western Hotels & Resorts
6201 N 24th Parkway, Phoenix, 85016, US
Last Update: 04/04/2026
Best Western Hotels & Resorts headquartered in Phoenix, Arizona, is a privately held hotel company within the BWH℠ Hotels global enterprise. With 19 brands and approximately 4,300 hotels in over 100 countries and territories worldwide*, BWH Hotels suits the needs of dev...
Whitbread
Whitbread Court, Houghton Regis, Dunstable, LU5 5XE, GB
Last Update: 20/05/2026
Whitbread PLC is the owner of the UK’s favourite hotel chain, Premier Inn, as well as restaurant brands, Beefeater, Brewers Fayre, Table Table, Bar + Block and Cookhouse and Pub. Whitbread employs more than 35,000 people in more than 1,200 Premier Inn hotels and restau...
Compliance Ranges Comparison
Best Western Hotels & Resorts
Whitbread
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Best Western Hotels & Resorts in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Whitbread in 2026.
Incident History - Best Western Hotels & Resorts (X = Date, Y = Severity)
Best Western Hotels & Resorts cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Whitbread (X = Date, Y = Severity)
Whitbread cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Best Western Hotels & Resorts
Whitbread
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: *.*.