Comparison Overview
Mahan Air

Mahan Air
Mahan Air Tower, Azadegan St., Karaj Highway, Tehran, Tehran, IR, 1481655761
Last Update: 13/03/2026
Mahan Air recognizes the dedication and diligence of 3300 staff as the key factor in our success. Every effort is made to create an exciting and rewarding working environment for them. To support our service excellence strategy, Mahan Air has adopted a rigorous quali...

AirAsia
AirAsia Berhad, RedQ, Jalan Pekeliling 5, KLIA2, Sepang, Selangor Darul Ehsan, MY, 64000
Last Update: 01/04/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...
Compliance Ranges Comparison

Mahan Air







AirAsia






Benchmark & Cyber Underwriting Signals
Incidents vs Airlines and Aviation Industry Avg (This Year)
No incidents recorded for Mahan Air in 2026.
Incidents vs Airlines and Aviation Industry Avg (This Year)
AirAsia has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Mahan Air (X = Date, Y = Severity)
Mahan Air cyber incidents detection timeline including parent company and subsidiaries.
Incident History - AirAsia (X = Date, Y = Severity)
AirAsia cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Mahan Air

AirAsia
FAQ
Latest Global CVEs
A vulnerability has been found in SourceCodester Simple Online Food Ordering System 1.0. This affects an unknown function of the file /admin/ajax.php?action=login2. The manipulation of the argument email leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
A flaw was found in the ipa_getkeytab module of the community.general Ansible collection. The module's bind_pw parameter, used to supply the LDAP simple-bind password when retrieving a Kerberos keytab, is not declared with no_log, unlike the sibling password parameter in the same module. As a consequence, the supplied IPA/LDAP bind password is recorded in cleartext in the managed host's system journal/syslog (the module's "Invoked with" record), is included in the module's return values and verbose (-v) output, and is displayed in Automation Controller / AWX job output. The password is additionally passed on the command line to the ipa-getkeytab helper (as --bindpw <value>), exposing it in the process list to local users while the command runs. An attacker able to read these logs, job output, or the process table can obtain the directory bind credential, potentially compromising the accounts and objects that credential can access.
The device metadata import interface /device/instance/{productId}/property-metadata/import of jetlinks community 2.11 is vulnerable to Server-side request forgery (SSRF).
disconf (Distributed Configuration Management Platform) 2.6.36 is vulnerable to Incorrect Access Control. The config-fetching APIs /api/config/item, /api/config/file, /api/config/list and /api/config/simple/list are exposed without authentication. The LoginInterceptor explicitly whitelists these four paths, so any anonymous attacker can read every configuration item and configuration file managed by the config center.
Funiture 1.0.0 is vulnerable to SQL Injection in the backend tool interfaces /sys/tool/select.json and /sys/tool/update.json.