Comparison Overview
Fraport Bulgaria
Fraport Bulgaria
Varna Airport, Varna , 9000, BG
Last Update: 04/02/2026
Fraport Bulgaria is the German-Bulgarian company awarded the 35-year concession for operating Burgas (BOJ) and Varna (VAR) airports. Fraport holds a majority 60-percent share in the joint company. In particular, Fraport Bulgaria is responsible for operating, managing a...
Alaska Airlines
19300 International Blvd, Seattle, 98188, US
Last Update: 31/03/2026
We’re creating an airline people love. It begins with each Alaska Airlines employee, bringing unique strengths and energy to our work in the air and on the ground. Every day, we go beyond what’s expected and reach for the remarkable, together. Welcome to our LinkedIn ...
Compliance Ranges Comparison
Fraport Bulgaria
Alaska Airlines
Benchmark & Cyber Underwriting Signals
Incidents vs Airlines and Aviation Industry Avg (This Year)
No incidents recorded for Fraport Bulgaria in 2026.
Incidents vs Airlines and Aviation Industry Avg (This Year)
No incidents recorded for Alaska Airlines in 2026.
Incident History - Fraport Bulgaria (X = Date, Y = Severity)
Fraport Bulgaria cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Alaska Airlines (X = Date, Y = Severity)
Alaska Airlines cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Fraport Bulgaria
Alaska Airlines
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: *.*.