Comparison Overview
Hospitality Solutions
Hospitality Solutions
3150 Sabre Drive, Southlake, TX, US, 76092
Last Update: 30/03/2026
Hospitality Solutions is now Aven Hospitality. Aven Hospitality, formerly Sabre Hospitality Solutions, is an independent global technology and SaaS leader in the hospitality industry, powering how hotels sell, distribute, and deliver guest experiences. SynXis, the lea...
Taj Hotels
9th Floor, Express Towers,, Mumbai, 400 021, IN
Last Update: 01/04/2026
Established in 1903, Taj is The Indian Hotels Company Limited’s (IHCL) iconic brand for the world’s most discerning travellers seeking luxury and authentic experiences. Taj has been rated as India’s Strongest Brand across all sectors for an unprecedented fourth time and...
Compliance Ranges Comparison
Hospitality Solutions
Taj Hotels
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Hospitality Solutions in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Taj Hotels in 2026.
Incident History - Hospitality Solutions (X = Date, Y = Severity)
Hospitality Solutions cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Taj Hotels (X = Date, Y = Severity)
Taj Hotels cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Hospitality Solutions
Taj 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: *.*.