SecurityThreats & vulnerabilitiesAnalysis

Amadeus breach hit at least ten airlines through one booking system

What Amadeus and the airlines disclosed from 23 October to 3 November: how one booking supplier exposed records at ten airlines, what was read, and why the counts cannot be added.

Illustration: The TechBag Journal

Amadeus, a Spanish company, runs the reservation systems of what Cathay Pacific calls “hundreds of airlines worldwide”.2 In the first half of 2026, 1,089.1 million passengers boarded flights of airlines using at least its reservation and inventory modules or its Navitaire system, by Amadeus’s own count.13 When something inside that supplier is misused, airlines learn second-hand, on the supplier’s timetable, and each tells its passengers in its own words. This piece puts the notices side by side: when each airline learned, how each describes the mechanism and the period, what each count measures, and what a passenger whose name and booking reference were read can do about it.

01Twenty-six days from detection to the first airline notice

According to ANA, Amadeus detected unauthorised third-party access to airline reservation information on 24 September, but did not report it to ANA that day. On 16 October ANA heard that another Amadeus airline had found unauthorised access and asked about its own flights; on 20 October Amadeus reported that access had been detected, and ANA informed Japan’s Personal Information Protection Commission, Aviation Wire reported.5 Korean Air says it was “officially notified by Amadeus on October 20, 2026, at 22:44 KST”; Asiana gives 22:49 the same night. Both published notices on 23 October.67 Japan Airlines and Japan Transocean Air were informed on 23 October and announced on 28 October; Cathay Pacific was notified on 28 October and received “further details” on 29 October.352 Qantas, which has not said its passengers were affected, quoted Amadeus as saying “the issue was contained in September”.12

Amadeus detected the access on 24 September; the airlines told passengers from 23 October to 3 November

Detection, notification of airlines and public disclosures in the Amadeus incident, 24 September to 3 November 2026

24 Sept 2026Amadeus detects access
20 Oct 2026First airlines told
23 Oct 2026Korean Air, Asiana publish
28 Oct 2026JAL announces; Cathay told
29 Oct 2026ANA and three partners
30 Oct 2026Cathay and ANA counts
31 Oct 2026Malaysia Airlines
3 Nov 2026Singapore Airlines
Show tableHide table
DateEventDetail
24 Sept 2026Amadeus detects accessANA's account: Amadeus did not tell ANA that day
20 Oct 2026First airlines toldKorean Air at 22:44 KST, Asiana at 22:49; ANA the same day, after asking on 16 October
23 Oct 2026Korean Air, Asiana publishSome booking references exposed; JAL and JTA informed the same day
28 Oct 2026JAL announces; Cathay toldAbout 92,000 JAL and JTA customers
29 Oct 2026ANA and three partnersAIRDO, Solaseed Air and StarFlyer hear from ANA
30 Oct 2026Cathay and ANA countsAbout 53,000 bookings; about 37,800 customers
31 Oct 2026Malaysia AirlinesCustomer information may be affected; no count
3 Nov 2026Singapore AirlinesAbout 46,000 booking records

Source: Airline notices (Korean Air, Asiana, JAL, ANA, StarFlyer, Cathay Pacific, Malaysia Airlines); ANA's account via Aviation Wire; SIA via CNA · as of 5 November 2026 · 24 September and the 20 October notice to ANA are ANA's account as reported by Aviation Wire

The regulators followed. Singapore’s Personal Data Protection Commission said on 4 November that it is investigating, and the Cyber Security Agency of Singapore said on 5 November that it is monitoring, The Straits Times reported. Cathay, Korean Air, Asiana and Singapore Airlines say they have informed their authorities; Qantas notified the Australian Cyber Security Centre.1126712

02One supplier under many airlines, and smaller airlines under those

Japan Airlines describes Amadeus as “the provider of our Passenger Service System (PSS) that integrates flight reservations, ticketing, and check-in procedures”.3 Amadeus’s own definition of its Altéa PSS is a system “used by full-service airlines to manage core operations such as reservations, inventory, ticketing, and departure control”. ANA finished moving onto it in the first half of 2026, when its domestic operations transferred.13 Some airlines reach Amadeus through another airline: AIRDO, Solaseed Air and StarFlyer use it via ANA, and learned of the incident from ANA on 29 October.58 A StarFlyer passenger was therefore told by StarFlyer, which was told by ANA, which was told by Amadeus.

A booking can pass through three companies, and the notice came back down the same chain

Where an affected booking sits, and how notice of the incident travelled, October and November 2026

  1. 01

    The passenger books

    With an airline or its partner. The booking, with its reference, lives in the airline’s passenger service system.

  2. 02

    Amadeus holds the record

    Reservations, ticketing and check-in for the host airline; partners such as StarFlyer reach it through ANA, and JTA sits in JAL’s notice.

  3. 03

    Something reads it

    A “booking display environment” with a vulnerability (Amadeus), or a system account’s login credentials (Cathay, Korean Air, Asiana).

  4. 04

    The notice runs back

    Amadeus to the airline, the airline to its partners and regulators, then email to passengers: 20 October to 3 November.

Source: JAL, ANA, StarFlyer, Cathay Pacific and Korean Air notices; Amadeus statement and H1 2026 management review; Aviation Wire · as of 5 November 2026

It has happened before. On 4 March 2021, SITA, another airline IT supplier, confirmed a cyber-attack on servers of SITA Passenger Service System (US) Inc., which “operates passenger processing systems for airlines”.15 Air India later said about 4.5 million of its customers were affected, with data registered between 26 August 2011 and 20 February 2021, including passport, ticket and credit-card details (but not CVV numbers), the BBC reported.16 Singapore Airlines counted about 580,000 KrisFlyer and PPS members whose membership numbers and tier status were exposed.11 The difference this time, on what has been published: neither Amadeus nor any airline has found evidence that payment data was accessed.

03Two accounts of how, and three readings of the same window

Amadeus’s statement is six sentences long. It does not use the words “credentials” or “account”, and it gives no count of airlines or passengers.1 The airlines’ notices, written from what Amadeus told them, describe something more specific. They are set out below without reconciling them, because neither side has explained the other.

Amadeus speaks of a display flaw; three airlines speak of a system account's login

How Amadeus and the airlines describe the mechanism and the containment, in their own words, October and November 2026

Amadeus: a vulnerability

  • “A vulnerability affecting a travel booking display environment”
  • “Certain booking-display data was accessible through the vulnerability”
  • “Measures to fix the vulnerability as well as enhanced monitoring and detection”
  • “No indications that this vulnerability has been exploited for ransomware purposes”

The airlines: a system account's login

  • Cathay: an unauthorised party “using login credentials assigned to its system account”
  • Korean Air: “unauthorized access using credentials assigned to Amadeus’s system accounts”; Asiana the same
  • Contained by “a password reset” (Cathay); the credentials “already invalidated” (ANA, StarFlyer)
  • Amadeus is “blocking unauthorized access and initiating dark web monitoring” (Korean Air)

Source: Amadeus statement (October 2026); Cathay Pacific (30 October), Korean Air and Asiana (23 October), ANA and StarFlyer (30 October) · as of 5 November 2026 · ANA, StarFlyer and Asiana quotes translated by TechBag

The two may describe one event from two ends: a login can be the way into a display tool. But nobody has said whose account it was, how its credentials were obtained, or why one account could read several airlines’ bookings. No one has publicly attributed the access to anyone, and we do not speculate.126748

The period is described three ways. JAL gives “August 10, 2023 – September 23, 2026” as the “period during which traces of external access were identified”.3 ANA uses the same dates for something else: customers who booked in that period.4 Cathay says the access “occurred between August 2023 and September 2026”; Korean Air says it is “estimated to have occurred” then, with the exact timing under investigation; Malaysia Airlines speaks of information “processed through Amadeus” in that period.269 StarFlyer’s window starts later, with bookings from 28 July 2025.8

04Three units, four counts, no total

Four airlines have published a number, and each counts something different. JAL and JTA count about 92,000 customers; ANA about 37,800 customers; Cathay about 53,000 bookings; Singapore Airlines about 46,000 booking records.34210 A booking can cover several passengers, and one passenger can hold several bookings, so the numbers cannot be summed into a count of people. Korean Air, Asiana, Malaysia Airlines, StarFlyer, AIRDO and Solaseed Air have given no count; StarFlyer says it is still checking.6795

Four airlines gave a count, in three different units, so there is no total

Records each airline says were accessed in the Amadeus incident, in the airline's own unit, as published 28 October to 3 November 2026

JAL and JTA customers92,000
Cathay Pacific bookings53,000
Singapore Airlines booking records46,000
ANA customers37,800
Show tableHide table
Value
JAL and JTA92,000
Cathay Pacific53,000
Singapore Airlines46,000
ANA37,800

Source: JAL (30 October), Cathay Pacific (30 October), Singapore Airlines via CNA (3 November), ANA (30 October) · as of 5 November 2026 · Each bar is in its own unit; bars are not comparable as people and must not be added

05A name and a booking reference are enough to open a booking

For most passengers, what was read is short: JAL lists the reservation code, name, flight date, sector and class of service for about 90,000 of its 92,000; ANA the same five items for about 36,100 of 37,800; Singapore Airlines names, booking references, itineraries and booking classes.3410 A small subset had more: email address, phone number, passport or travel-document number, nationality and frequent-flyer number. Credit-card numbers and passwords were not among them, the Japanese airlines say.34

At most one record in twenty also held contact or passport details

Share of each airline's affected records that also held email, phone, travel-document or frequent-flyer data, %, as published 30 October to 3 November 2026

4.5%

ANA

about 1,700 of 37,800 customers

2.2%

JAL and JTA

about 2,000 of 92,000 customers

1.3%

Singapore Airlines

about 620 of 46,000 booking records

Source: JAL and ANA notices (30 October); Singapore Airlines via CNA (3 November); shares computed by TechBag · as of 5 November 2026 · JAL 2,000 of 92,000 customers; ANA 1,700 of 37,800 customers; SIA 620 of 46,000 booking records. Cathay gave no split

The short records still matter. Cathay’s own help page tells non-members to “simply provide your name and booking reference number or e-ticket number to retrieve your booking on Manage Booking”, where a booking can be changed or cancelled.17 That is why Singapore Airlines is contacting customers with upcoming travel to change their booking reference numbers. Amadeus has confirmed that no booking was modified, the airline said; ANA says Amadeus found no evidence of data being altered or deleted.105 The other risk is a message that already knows your flight. JAL asks customers “to remain vigilant against phishing emails, fraudulent phone calls, and suspicious websites impersonating the JAL Group”; Korean Air asks them to “refrain from clicking unfamiliar links”.36

Sources

  1. Amadeus, Data and Vulnerability Statement — October 2026 Text last modified 2 November 2026.
  2. Cathay Pacific, Personal data security incident involving a third-party service provider — 30 October 2026, 16:11 HKT
  3. Japan Airlines and Japan Transocean Air, Regarding Unauthorized Access to Amadeus Passenger Service System and Our Response — 30 October 2026 First announced 28 October (Aviation Wire).
  4. ANA, Amadeus社 旅客サービスシステムへの不正アクセスについて (Unauthorised access to Amadeus's passenger service system) — 30 October 2026 Japanese; quoted in TechBag's translation.
  5. Aviation Wire, ANA、不正アクセス影響3.8万人 1700人はパスポート番号も=アマデウス問題 (ANA: 38,000 affected, 1,700 with passport numbers) — 30 October 2026
  6. Korean Air, notice on a potential personal data security incident at Amadeus — 23 October 2026
  7. Asiana Airlines, 일부 고객 개인정보(예약번호) 유출 안내 (Notice of leak of some customers' booking numbers) — 23 October 2026 Korean; quoted in TechBag's translation.
  8. StarFlyer, Amadeus社が提供する旅客サービスシステムへの不正アクセスについて (Unauthorised access to the Amadeus passenger service system) — 29 October 2026, updated 30 October 2026 Japanese; quoted in TechBag's translation.
  9. Malaysia Airlines, Cybersecurity incident involving third-party technology provider — 31 October 2026
  10. CNA, About 46,000 SIA booking records accessed in data breach involving travel tech company Amadeus — 3 November 2026
  11. The Straits Times, About 46,000 SIA booking records accessed illegally in data breach affecting software provider Amadeus — 3 November 2026, updated 5 November 2026
  12. Australian Aviation, Qantas customer data possibly exposed in Amadeus hack — 2 November 2026
  13. Amadeus, Management review, results for the six months ended 30 June 2026 (passengers boarded; Altéa PSS; ANA migration) — 31 July 2026
  14. Amadeus, Investors page (Q3 2026 results, 6 November 2026) — November 2026
  15. SITA, SITA statement about security incident — 4 March 2021
  16. BBC News, Air India cyber-attack: Data of millions of customers compromised — 22 May 2021
  17. Cathay Pacific, Manage Booking (India site): retrieving a booking with name and booking reference — undated help page
  18. Digital Personal Data Protection Act, 2023, section 8(5) and 8(6) — 11 August 2023
  19. MeitY, Digital Personal Data Protection Act, 2023 and DPDP Rules, 2025 (notified 13 November 2025; Rule 7 from 13 May 2027) — 13 November 2025
  20. CERT-In, Directions under section 70B(6) of the IT Act (six-hour reporting; Annexure I items xi and xii, Data Breach and Data Leak) — 28 April 2022

Related on TechBag: the privileged access guide, on the controls for system and service accounts.

Disclosure. TechBag is a software reseller: it earns a margin when a reader buys through it, including from vendors named here. The analysis is TechBag’s own; no vendor paid for or saw this piece before publication. Facts are labelled reported, TechBag count or our view.