Comparison Overview
Crowne Plaza Today, Gurugram
Crowne Plaza Today, Gurugram
Sector 29, National Highway – 8,, Gurgaon- 122001, Haryana, 122001, IN
Last Update: 10/12/2025
Crowne Plaza Today, Gurugram offers a unique location advantage to its corporate and leisure patrons by hosting them in the city centre of this millennium city, in close proximity to the domestic and international airport and right next to the 8 Lane expressway that con...
Aramark
2400 Market St, Philadelphia, 19103, US
Last Update: 02/04/2026
Aramark (NYSE: ARMK) proudly serves the world’s leading educational institutions, Fortune 500 companies, world champion sports teams, prominent healthcare providers, iconic destinations and cultural attractions, and numerous municipalities in 16 countries around the wor...
Compliance Ranges Comparison
Crowne Plaza Today, Gurugram
Aramark
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Crowne Plaza Today, Gurugram in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Aramark in 2026.
Incident History - Crowne Plaza Today, Gurugram (X = Date, Y = Severity)
Crowne Plaza Today, Gurugram cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Aramark (X = Date, Y = Severity)
Aramark cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Crowne Plaza Today, Gurugram
Aramark
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: *.*.