Comparison Overview
Clarion Hotels
Clarion Hotels
1 Choice Hotels Cir, Rockville, MD, 20850, US
Last Update: 22/04/2026
The Clarion® brand, by Choice Hotels, believes life is better when you get together. Clarion hotels make it convenient to connect. Plus, we offer plenty of amenities when it’s time to unwind. Explore the lounge, bar and full-service restaurant, dive into the pool, work ...
Travel + Leisure Co.
6277 Sea Harbor Dr, Orlando, Florida, US, 32821
Last Update: 01/04/2026
Travel + Leisure Co., the world's leading vacation ownership and membership travel company, provides more than six million vacations to travelers every year. The company’s extensive Vacation Ownership portfolio includes trusted and iconic vacation club brands with a com...
Compliance Ranges Comparison
Clarion Hotels
Travel + Leisure Co.
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Clarion Hotels in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Travel + Leisure Co. in 2026.
Incident History - Clarion Hotels (X = Date, Y = Severity)
Clarion Hotels cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Travel + Leisure Co. (X = Date, Y = Severity)
Travel + Leisure Co. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Clarion Hotels
Travel + Leisure Co.
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: *.*.