“No evidence that financial or payment information was accessed” is a familiar reassurance after a data breach. Cathay Pacific used that formulation in its notice, and Japan Airlines said credit card numbers were not compromised. The statements answer an important question. In the Amadeus incident, they leave the more consequential questions open.
For some passengers, the greatest harm could come from exposure of their identity, movements and associations. Assessing this incident primarily through the lens of payment fraud risks understating what passenger reservation data can reveal.
What has been confirmed
Japan Airlines (JAL) disclosed in its English notice dated 30 October unauthorised access affecting approximately 92,000 customers of JAL and Japan Transocean Air. The exposed information included booking references, names, flight dates and flight details. For approximately 2,000 of those customers, the information potentially also included passport numbers, nationality, email addresses, phone numbers, frequent flyer numbers, ticket numbers and seat numbers. JAL identifies traces of external access between 10 August 2023 and 23 September 2026.[1]
Cathay Pacific separately disclosed on 30 October approximately 53,000 affected bookings (not necessarily 53,000 passengers). It says an unauthorised party used credentials assigned to an Amadeus system account. Most affected records involved names, booking references and flight details; a smaller subset potentially included contact details, travel document information or frequent flyer numbers.[2]
All Nippon Airways (ANA) reported about 37,800 affected customers, with additional information, including passport numbers and nationality, potentially compromised for about 1,700 of them.[3] Korean Air and Asiana each issued notices on 23 October. Both confirmed exposure of booking references, and Asiana said other potentially exposed fields remained under investigation.[4][5][7] Air Do, Solaseed Air and Starflyer, which use Amadeus through ANA, have said they were told of possible exposure.[6] The full airline scope remains unclear.
These disclosures establish exposure of reservation data. They do not establish that every field in every affected Passenger Name Record was accessed, or that access was continuous throughout the reported period. The reported period is also described differently by different carriers: Cathay and JAL describe it as the period of access, while ANA describes it as the period in which affected customers made bookings.
The technical cause remains unresolved publicly. Cathay Pacific and Korean Air describe unauthorised use of login credentials assigned to an Amadeus system account.[2][4] Amadeus's own statement refers instead to a vulnerability affecting a travel booking display environment, which it says it has fixed, and does not mention credentials.[12] The disclosures do not fully explain how those credentials were obtained and used, or whether the compromised access allowed changes to records.
A PNR is more than a booking reference
A booking reference identifies a reservation. The Passenger Name Record behind it can hold considerably more information about the traveller and their journey.
The Australian Border Force describes PNR data as potentially including names, contact details, itinerary, ticketing information and collected Advance Passenger Information, such as passport details, date of birth and nationality. Home Affairs uses PNR analysis as part of its intelligence-led approach to border protection.[8]
That use illustrates its analytical value. In hostile hands, travel information can also help someone understand a person's movements and build a profile of their activities.
The following are potential consequences of PNR exposure, not findings that these activities occurred in the Amadeus incident.
Free-text fields can contain sensitive personal information
PNRs can also contain free-text remarks, Other Service Information (OSI) and Special Service Requests (SSR), including fields that combine standard codes with explanatory text. These allow airlines and travel agents to record information needed to support a passenger's journey.[9][10]
Depending on what has been entered, those fields may reveal health conditions, disability, mobility or assistance needs, and other personal circumstances. Meal requests may also suggest religious observance or a health requirement, although a preference alone does not establish either. ICAO recognises that PNR free text, general remarks, meal preferences and health information can contain sensitive data requiring appropriate protection.[9]
The risk therefore extends beyond the named fields in a breach notice. A description such as “reservation information” may not tell an affected passenger whether intimate details recorded in a remark or service request were exposed. Assessment needs to examine the actual contents of these fields, with safeguards for the reviewers handling them.
The public disclosures reviewed here do not confirm that free-text remarks, OSI or SSR contents were accessed. That remains a specific question for the investigation, rather than an established fact about this incident.
Travel history can become intelligence
An itinerary can reveal a named person's intended movements. Check-in or boarding information, where available, may provide stronger evidence of actual travel. A reservation alone does not prove that a journey took place. Multiple records, combined with public information or other compromised datasets, could reveal recurring destinations, routines and possible relationships.
For executives, diplomats, Defence personnel, journalists and investigators, those patterns may expose sensitive activity. Repeated travel to a location could provide clues about negotiations, projects or assignments. Shared reservations, where exposed, could reveal companions; coincident travel alone would require corroboration before drawing conclusions about an association.
Historical information still matters. A journey that ended years ago can remain useful when reconstructing someone's activities or identifying people connected to them.
Accurate details make impersonation more convincing
A fraudulent caller who knows your flight, travel date and booking reference has a credible opening. They could impersonate an airline, travel agent or corporate travel desk and invent an urgent problem with the booking.
The same details could strengthen an approach to an executive assistant or helpdesk. Knowledge of a genuine journey can make a false request feel verified before anyone has actually authenticated the requester.
For a person facing stalking, coercive control or targeted harassment, travel information may also create a personal safety risk. Exposure of future travel, if present in affected records, would require particular urgency. The reviewed public notices do not establish whether future itineraries were exposed.
Identity exposure can outlast the trip
Passport numbers, nationality and contact details add to the value of reservation data for identity profiling and impersonation. Exposure does not automatically allow someone to travel using another person's identity, but it gives an adversary more material to combine with other sources.
A payment card can usually be cancelled and replaced. Historical movements and disclosed relationships cannot be recalled. Even replacing an identity document does not erase the associations already revealed.
The response needs to reflect the data
Airlines and their providers should explain which fields were accessed, whether records included future travel or linked passengers, and whether the compromised access allowed reading only or also changes. They should explicitly address free-text remarks, OSI and SSR contents, rather than relying on broad labels such as “booking data”. Those distinctions determine the potential harm. Airlines and travel agents should also record only the personal information necessary to deliver the requested service, especially in free-text fields.
Organisations should assess affected staff according to their role and circumstances, including travel sensitivity and personal safety. Travel desks, executive assistants and helpdesks should treat accurate itinerary knowledge as information a caller might possess, not proof of identity.
PNRGOV is the airline-to-government message standard for transferring PNR data.[11] Exposure of airline reservation data does not establish compromise of those messages, their transmission services or government receiving systems; the incident disclosures cited here do not confirm that broader compromise.
Breach communications should give identity, location and association data the attention their consequences warrant. For some affected passengers, an intact bank account may be the least reassuring measure of whether they are safe.
