Comparison Overview
Asiana Airlines
Asiana Airlines
Asiana Town, Gangseo-Gu, 157-713, KR
Last Update: 19/03/2026
(Overview) Asiana Airlines is an airline based in Seoul, Korea. As a member of the Star Alliance, Asiana operates over 90 routes to 77 cities in 21 countries worldwide. (Mission) Fullfilling customer satisfaction by providing the best in safety, services, and comfo...
Aeromexico
MX
Last Update: 03/04/2026
Grupo Aeromexico, S.A.B. de C.V. is a holding company whose subsidiaries are engaged in commercial aviation and the promotion of passenger loyalty programs in Mexico. Aeromexico, Mexico’s global airline, operates more than 600 daily flights and has its main hub in Termi...
Compliance Ranges Comparison
Asiana Airlines
Aeromexico
Benchmark & Cyber Underwriting Signals
Incidents vs Airlines and Aviation Industry Avg (This Year)
No incidents recorded for Asiana Airlines in 2026.
Incidents vs Airlines and Aviation Industry Avg (This Year)
No incidents recorded for Aeromexico in 2026.
Incident History - Asiana Airlines (X = Date, Y = Severity)
Asiana Airlines cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Aeromexico (X = Date, Y = Severity)
Aeromexico cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Asiana Airlines
Aeromexico
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: *.*.