Comparison Overview
Restaurant Associates Australia
Restaurant Associates Australia
35-51 Mitchell St, Mcmahons Point, New South Wales, 2060, AU
Last Update: 05/12/2025
Restaurant Associates elevate employee and guest experiences through premium hospitality, bespoke menus and exceptional services. We work with our partners and collaborate with our clients to achieve great things together. Channelling a deep-rooted culture of creativ...
Kempinski Hotels
Maximilianstrasse 17, Munich, 80539, DE
Last Update: 01/04/2026
Founded in Germany in 1897, Kempinski Hotels has long reflected the finest traditions of European hospitality. Today, as ever, Kempinski is synonymous with distinctive luxury. Located in many of the world's most well-known cities and resorts, the Kempinski collection i...
Compliance Ranges Comparison
Restaurant Associates Australia
Kempinski Hotels
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Restaurant Associates Australia in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Kempinski Hotels in 2026.
Incident History - Restaurant Associates Australia (X = Date, Y = Severity)
Restaurant Associates Australia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Kempinski Hotels (X = Date, Y = Severity)
Kempinski Hotels cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Restaurant Associates Australia
Kempinski Hotels
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: *.*.