Comparison Overview
Fraport AG

Fraport AG
Frankfurt am Main, 60547, DE
Last Update: 14/03/2026
Die Fraport AG gehört zu den international führenden Unternehmen im Airport-Business und ist an 29 Flughäfen auf vier Kontinenten aktiv. Im Jahr 2025 begrüßte Fraport am Flughafen Frankfurt 63,2 Millionen Passagiere. Das Cargo-Volumen lag bei rund 2,1 Millionen Tonnen. ...

Southwest Airlines
2702 Love Field Drive, Dallas, 75235, US
Last Update: 20/05/2026
At Southwest®, everything we do—from our smiling People to our policies—is designed to let you go with Heart. No matter what comes up in your travels, we’ve got your back. Because while any airline can fly you, only Southwest lets you go with Heart. Application fees do...
Compliance Ranges Comparison

Fraport AG







Southwest Airlines






Benchmark & Cyber Underwriting Signals
Incidents vs Airlines and Aviation Industry Avg (This Year)
No incidents recorded for Fraport AG in 2026.
Incidents vs Airlines and Aviation Industry Avg (This Year)
No incidents recorded for Southwest Airlines in 2026.
Incident History - Fraport AG (X = Date, Y = Severity)
Fraport AG cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Southwest Airlines (X = Date, Y = Severity)
Southwest Airlines cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Fraport AG

Southwest 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: *.*.