Comparison Overview
Liberty Travel
Liberty Travel
5 Paragon Drive, Suite 200, Montvale, NJ, 07645, US
Last Update: 30/12/2025
Real people helping real people. Beside you every step of the way. For over 70 years, the person-to-person experience has been at the very core of Liberty Travel’s mission. It's what we've always done, and now it’s more important than ever. To ensure your next vacatio...
Enterprise Mobility
600 Corporate Park Drive, St. Louis, Missouri, US, 63105
Last Update: 04/04/2026
At Enterprise Mobility™ we are paving a new way forward by creating better experiences for how we move. We give people around the world the ability to connect in ways that suit their unique needs. It’s a bold idea that has defined our purpose-led, people-first organizat...
Compliance Ranges Comparison
Liberty Travel
Enterprise Mobility
Benchmark & Cyber Underwriting Signals
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for Liberty Travel in 2026.
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for Enterprise Mobility in 2026.
Incident History - Liberty Travel (X = Date, Y = Severity)
Liberty Travel cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Enterprise Mobility (X = Date, Y = Severity)
Enterprise Mobility cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Liberty Travel
Enterprise Mobility
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: *.*.