Comparison Overview
Aspire Lifestyles
Aspire Lifestyles
111 Town Square Pl, Jersey City, New Jersey, 07310, US
Last Update: 27/02/2026
The best stories are told by those who have lived the experience. Our mission is to inspire and delight your customers by making amazing stories happen every day. Stories they can share with their friends, family and colleagues. Stories that reinforce the value of your ...
Royal Caribbean Group
Royal Caribbean Group 1050 Caribbean Way Miami, Miami, Florida, US, 2312
Last Update: 01/04/2026
At Royal Caribbean Group, we deliver unforgettable vacations to guests who trust us with life’s greatest moments. We build the best ships, and even better careers, all while doing the right thing. We are passionate. We are innovative. We are unstoppable. We open the wor...
Compliance Ranges Comparison
Aspire Lifestyles
Royal Caribbean Group
Benchmark & Cyber Underwriting Signals
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for Aspire Lifestyles in 2026.
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for Royal Caribbean Group in 2026.
Incident History - Aspire Lifestyles (X = Date, Y = Severity)
Aspire Lifestyles cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Royal Caribbean Group (X = Date, Y = Severity)
Royal Caribbean Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Aspire Lifestyles
Royal Caribbean Group
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: *.*.