Comparison Overview
P&O Cruises
P&O Cruises
Carnival House, Southampton, SO15 1ST, SO15 1ST, GB
Last Update: 22/02/2026
P&O Cruises is Britain’s favourite cruise line, welcoming guests to experience holidays with a blend of discovery, choice, relaxation and exceptional service catered towards British tastes. The fleet of seven ships each have their own appeal from family friendly or excl...
Europcar Mobility Group
13 ter Boulevard Berthier, Paris, Île-de-France, FR, 75017
Last Update: 29/03/2026
Europcar Mobility Group is a global mobility player, with 75 years of mobility services expertise and a leading position in Europe. “We help to change the way you move” is what we stand for and brings us together. More than ever, we're committed to delivering simple, s...
Compliance Ranges Comparison
P&O Cruises
Europcar Mobility Group
Benchmark & Cyber Underwriting Signals
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for P&O Cruises in 2026.
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for Europcar Mobility Group in 2026.
Incident History - P&O Cruises (X = Date, Y = Severity)
P&O Cruises cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Europcar Mobility Group (X = Date, Y = Severity)
Europcar Mobility Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
P&O Cruises
Europcar Mobility 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: *.*.