Comparison Overview
AirAsia
AirAsia
AirAsia Berhad, RedQ, Jalan Pekeliling 5, KLIA2, Sepang, Selangor Darul Ehsan, MY, 64000
Last Update: 04/09/2026
It all starts here. 23 years ago, a dream took flight - shaping and forever changing the travel industry in Asia. The idea was simple: Make flying affordable for everyone. We made that dream happen. We started an airline in 2001. Today, we’ve evolved to become somethi...
Menzies Aviation
21-22 Bloomsbury Square, London, England, GB
Last Update: 13/09/2026
People. Passion. Pride. These have driven our team since 1833. Since that time, we have developed to become a critical partner in the global aviation industry, delivering time-critical logistics services at over 350 locations in 65 countries, across six continents...
Compliance Ranges Comparison
AirAsia
Menzies Aviation
Benchmark & Cyber Underwriting Signals
Incidents vs Airlines and Aviation Industry Avg (This Year)
AirAsia has 55.36% 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 Menzies Aviation in 2026.
Incident History - AirAsia (X = Date, Y = Severity)
AirAsia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Menzies Aviation (X = Date, Y = Severity)
Menzies Aviation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
AirAsia
Menzies Aviation
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout