Comparison Overview
Wingbuddy
Wingbuddy
225 Rue Chabanel O, Montreal, H2N 2C9, CA
Last Update: 17/03/2026
Wingbuddy is a leading tour operator and online travel agency specializing in providing hassle-free travel experiences. We are passionate about inspiring North Americans to maximize their travel experiences with our turnkey packages to worldwide destinations. Whether it...
Norwegian Cruise Line Holdings Ltd.
7665 Corporate Center Drive, Miami, 33126, US
Last Update: 02/04/2026
Norwegian Cruise Line Holdings Ltd. (NYSE: NCLH) is a leading global cruise company which operates Norwegian Cruise Line, Oceania Cruises and Regent Seven Seas Cruises. With a combined fleet of 32 ships and approximately 66,500 berths, NCLH offers itineraries to appro...
Compliance Ranges Comparison
Wingbuddy
Norwegian Cruise Line Holdings Ltd.
Benchmark & Cyber Underwriting Signals
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for Wingbuddy in 2026.
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for Norwegian Cruise Line Holdings Ltd. in 2026.
Incident History - Wingbuddy (X = Date, Y = Severity)
Wingbuddy cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Norwegian Cruise Line Holdings Ltd. (X = Date, Y = Severity)
Norwegian Cruise Line Holdings Ltd. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Wingbuddy
Norwegian Cruise Line Holdings Ltd.
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: *.*.