Comparison Overview
Malaysia Airlines
Malaysia Airlines
Kuala Lumpur International Airport, Sepang, 64000, MY
Last Update: 12/03/2026
Malaysia Airlines is the national carrier of Malaysia, serving 40,000 guests on 330 flights to more than 50 destinations daily. Malaysia Airlines operates flights from its home base, Kuala Lumpur International Airport, and offers connectivity across the globe; includ...
Ethiopian Airlines
Bole International Airport, Addis Ababa, 1755, ET
Last Update: 04/04/2026
Ethiopian Airlines Group (Ethiopian) is a true African success story, transforming a visionary dream into a globally renowned reality for nearly eight decades. Operating flights to more than 160 domestic and international passenger, and cargo destinations across five co...
Compliance Ranges Comparison
Malaysia Airlines
Ethiopian Airlines
Benchmark & Cyber Underwriting Signals
Incidents vs Airlines and Aviation Industry Avg (This Year)
Malaysia Airlines has 55.16% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Airlines and Aviation Industry Avg (This Year)
No incidents recorded for Ethiopian Airlines in 2026.
Incident History - Malaysia Airlines (X = Date, Y = Severity)
Malaysia Airlines cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ethiopian Airlines (X = Date, Y = Severity)
Ethiopian Airlines cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Malaysia Airlines
Ethiopian 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: *.*.