Comparison Overview
Renaissance Phoenix Glendale Hotel & Conference Center
Renaissance Phoenix Glendale Hotel & Conference Center
9495 W. Coyotes Blvd., Glendale, 85305, US
Last Update: 18/02/2026
Located just steps from the State Farm Stadium, Gila River Arena and Westgate Entertainment District, the Renaissance Phoenix Glendale Hotel & Spa is the perfect place to Live Life to Discover!
Holiday Inn
3 Ravinia Dr, Atlanta, 30346, US
Last Update: 01/04/2026
More than an iconic place to stay, Holiday Inn Hotels are a place to be in the moment–gathered to celebrate with family, laughing with friends, sharing a meal with the team, or just for some well-deserved me-time. No matter the reason you travel, when you’re here, you’r...
Compliance Ranges Comparison
Renaissance Phoenix Glendale Hotel & Conference Center
Holiday Inn
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Renaissance Phoenix Glendale Hotel & Conference Center in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Holiday Inn in 2026.
Incident History - Renaissance Phoenix Glendale Hotel & Conference Center (X = Date, Y = Severity)
Renaissance Phoenix Glendale Hotel & Conference Center cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Holiday Inn (X = Date, Y = Severity)
Holiday Inn cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Renaissance Phoenix Glendale Hotel & Conference Center
Holiday Inn
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: *.*.