In a notification to Sweden's Authority for Privacy Protection (IMY), SAS said booking data for 350,164 of its travelers may have been exposed through Amadeus. The same notification records its decision not to tell them. The airline judges the incident not to be high risk under the General Data Protection Regulation, because the records mostly cover older bookings and completed trips.
This updates my earlier analysis of how Amadeus was breached for three years and Japan Airlines sent the apology. That piece argued the airlines answer for an intrusion inside infrastructure they do not run. In the nine days since, Thai Airways joined them, and the list moved from Asia into Europe.
On November 9, Thai Airways said about 60,529 passenger booking records may have been accessed without authorization. About 376 further records may also include passport numbers and contact details. The access window runs from August 10, 2023 to September 23, 2026, the same dates Japan Airlines and ANA gave. Amadeus revoked the log-in credentials used and reset the affected passwords.
Thai Airways says it will contact affected passengers individually. The Civil Aviation Authority of Thailand (CAAT) instructed it to tell passengers promptly to change log-in passwords and amend booking details. That instruction treats a booking reference as a live access token. Paired with a passenger surname, a reference for an upcoming trip can open the itinerary to changes, and real booking details make fraudulent messages far more convincing.
Europe followed the same week. Finnair says about 116,000 Finnair reservations appeared on flight lists involved in the breach, and roughly 750 of them were opened. It issued new reservation numbers for the opened bookings still active. Norwegian told Norway's Data Protection Authority (Datatilsynet) the breach affects 144,249 Norwegian and Widerøe passengers. Qantas, absent from my original analysis, said on November 4 it was working with Amadeus to understand the impact on its bookings.
My original tally of publicly quantified figures stood at roughly 228,800. With Thai Airways, Finnair, SAS, Norwegian, and Widerøe added, published figures now pass 900,000 customers, passengers, reservations, and booking records. The total marks an exposure ceiling and says nothing about how many records were copied. Finnair's figures show the gap, with 116,000 reservations on affected flight lists and roughly 750 opened. The airlines also count in different units, and one traveler can appear under several carriers.
That duplication cuts both ways. It inflates the headline count, but it strengthens the data for anyone holding it. A traveler appearing across several airlines, routes, and dates gives a threat actor a fuller movement history. Shared names, contact details, and passport numbers can join separate bookings into one identity.
The notification decisions now diverge across the same intrusion. Thai Airways notifies passengers individually. Finnair says Amadeus, as data controller for the affected service, is responsible for informing individuals, while Finnair will email customers whose contact details Amadeus supplies. Amadeus's own privacy statement describes it as the independent data controller for traveler data in its global distribution system.
SAS will not notify its 350,164 travelers unless new information changes its risk assessment. Norwegian is still deciding whether the breach is serious enough to contact passengers at all. Part of the split may reflect the data each airline holds. Thai Airways has hundreds of records carrying passport and contact details, while SAS says its records mostly cover older, completed trips.
The airline statements and Norway's government also describe the fate of the data differently. Thai Airways says it has identified no disclosure of the data so far. Norway's National Security Authority (NSM) says it knows sensitive data has leaked. NSM told Norwegian organizations to assess the risk to trips booked before September 23 and to change their log-in credentials at travel agencies. An airline identifying no disclosure of its records does not mean the records stayed inside Amadeus.
The warning came from Norway's national security authority, not only from its privacy regulator. That fits the risk I raised in the original analysis, where travel records serve as pattern-of-life intelligence. Depending on the booking, NSM says the exposed data may include passport numbers, nationality, contact details, seat reservations, and free-text entries. Three years of those records show who travels where, when, with whom, and how often.
NSM's advice also points past the airlines to the travel agencies. NSM says most of Norway's travel industry relies on Amadeus systems, and it names Berg-Hansen and Egencia among the users. Berg-Hansen notified Datatilsynet of its own breach connected to the incident. Corporate travel agencies organize bookings around an employer rather than a carrier. Their records can show which employees travel together, which organizations meet, and where a team keeps returning. An airline record covers one leg of a journey, while an agency account can expose the purpose behind it.
The access path remains unresolved. Airline disclosures describe compromised credentials assigned to an Amadeus system account, and SAS says the intruder used those credentials to enter the booking system, then carried out automated searches. Automation points to repeated, systematic querying of the booking data. Amadeus describes a vulnerability affecting a travel booking display environment and says it has seen no indication of ransomware. The credentials may have supplied entry while the vulnerability widened what the account could retrieve, but no published evidence establishes that sequence.
The timing keeps the question open. In October, Heise reported an unauthenticated heap dump in an Amadeus environment exposing plaintext credentials, authentication tokens, and administrator passwords. Amadeus was alerted on September 21, and the airline access window closes on September 23, two days later.
Thailand's response targets access controls. The Transport Ministry ordered aviation agencies and service providers holding personal data to tighten access controls, strengthen password management, and adopt technology to detect wrongdoing. CAAT also identified six other affected airlines, all already named in my original analysis. The order addresses the credential half of the access path, but it cannot reach the vulnerability inside Amadeus.
No airline, regulator, or Amadeus statement has disclosed how the credentials were obtained or why the access lasted 37 months. No threat actor has been named, and no one has claimed responsibility or offered the data for sale. Three years of quiet, automated searching through travel records fits an intelligence operation. It also fits patient criminal harvesting, and the public record shows what the account could reach without showing whom the intruder chose to search for.
My original analysis asked who apologizes when a vendor is breached. The disclosures since then show a harder problem. Responsibility is spread across Amadeus, the airlines, the travel agencies, and national regulators, each with a different legal role and a different slice of the data. A traveler on Thai Airways gets a notice, and the same traveler on SAS gets nothing, after exposure through the same platform.
I assess with high confidence the Thai Airways, Finnair, SAS, Norwegian, and Widerøe disclosures stem from the same Amadeus intrusion described in my original analysis, given the shared vendor and the matching access window. I assess with moderate confidence data from the intrusion has left Amadeus, based on NSM's statement and despite no published sample. I assess with low confidence the access served espionage rather than criminal collection, and no public evidence supports attribution to any threat actor.
Analyst Annex
Evidence status as of November 15, 2026. The records cover airline disclosures published from October 23 through November 13, Amadeus statements, government warnings, and regulatory reporting. Each airline remains a separate record because published figures count customers, bookings, records, and flight-list entries differently.
Government bodies and travel agencies appear only where they supplied evidence, responded, or show the affected travel ecosystem. The ATT&CK mapping covers the credential-misuse incident and does not map exfiltration, because no source discloses a method, although NSM states sensitive data has leaked. The Indicators subsection is omitted because no incident-specific infrastructure, files, accounts, or cryptographic hashes have been published. Separate Amadeus and SITA security events appear only under Related Activity.
Intelligence Gaps
| Gap | Why It Matters | What Would Close It |
|---|---|---|
| How the credentials were obtained | The answer would locate the original weakness in Amadeus account management, a customer or agency environment, or credential theft elsewhere. It would also show whether other Amadeus customers remain exposed | Amadeus forensic findings, regulator findings, or the provenance of the account and credentials |
| Relationship between the booking-display vulnerability and credential misuse | Amadeus describes a fixed vulnerability in a booking-display environment. Airline disclosures describe access through valid system-account credentials. Amadeus learned of the exposed heap dump on September 21, 2026, and the airline access window ends two days later, on September 23. Public reporting does not establish whether these events form one intrusion path | An Amadeus technical report linking or separating the vulnerability, the exposed memory data, and the credential-based access |
| Reason the access remained undetected for as long as 37 months | Access traces begin August 10, 2023, and Amadeus closed the access on September 23, 2026. The monitoring failure affects the risk carried by every customer sharing the environment | The detection timeline, log-retention period, account-use history, and audit findings |
| Whether one credential set supplied the entire access period | The published dates define the possible exposure window. They do not show continuous access or prove the same account remained usable throughout it | Authentication records showing the accounts, sessions, source locations, and dates involved |
| Identity and motive of the threat actor | Espionage, eCrime resale, targeted fraud, and opportunistic collection create different downstream risks. No government, airline, or vendor has attributed the activity | Attribution supported by Amadeus telemetry, government reporting, or a credible claim backed by validated data |
| Whether and where the data has surfaced | NSM states sensitive data leaked. Thai Airways reported finding no disclosure as of November 9. The difference may reflect separate visibility rather than conflicting evidence | NSM detail on the basis for its statement, or a validated dataset found in criminal infrastructure or a marketplace |
| Full list of affected airlines and travel agencies | Amadeus serves airlines and travel agencies worldwide. Disclosures have appeared one organization and jurisdiction at a time | A complete customer-impact list from Amadeus or a lead regulator |
| Number of unique individuals affected | Published figures mix customers, bookings, records, and flight-list entries. One traveler can appear in several airline datasets | A deduplicated count from Amadeus with a common unit of measurement |
| Distribution of passport and travel-document data | Japan Airlines, ANA, Singapore Airlines, and Thai Airways publish sensitive-subset figures. Other disclosures leave the number of passport-bearing records unclear | Per-airline counts of records containing passport, nationality, contact, and special-service fields |
Entities
| Entity | Type | Role | Status | Source |
|---|---|---|---|---|
| Amadeus IT Group | Travel technology provider | Operates the passenger-service environment holding the accessed booking records. Airline disclosures state Amadeus revoked the credentials used, reset affected passwords, and strengthened monitoring. Says it has found no evidence of payment or financial data accessed and no indication of ransomware. Finnair identifies Amadeus as data controller for the affected service, and Amadeus describes itself as the independent data controller for traveler data in its global distribution system | Confirmed | Amadeus, Amadeus privacy statement, Cathay Pacific, Finnair, Nation Thailand |
| Unidentified threat actor | Threat actor, unknown | Used credentials assigned to an Amadeus system account to access passenger booking data during an exposure window extending from August 10, 2023 through September 23, 2026. No attribution or credible claim of responsibility has been published | Reported | Cathay Pacific, NSM |
| Japan Airlines and Japan Transocean Air | Airline | About 92,000 customers affected. About 2,000 within that total also had contact details, passport numbers, nationality, frequent-flyer numbers, and additional flight data exposed | Confirmed | Japan Airlines |
| ANA | Airline | About 37,800 customers affected. About 1,700 within that total also had passport numbers and nationality exposed | Confirmed | ANA |
| Korean Air | Airline | Disclosed some customer booking references were exposed through unauthorized use of credentials assigned to an Amadeus system account. Reported finding no evidence of intrusion into its own databases | Confirmed | Korean Air, MoneyToday |
| Cathay Pacific | Airline | About 53,000 bookings affected. Its disclosure states the threat actor used credentials assigned to an Amadeus system account | Confirmed | Cathay Pacific |
| Singapore Airlines | Airline | About 46,000 booking records affected. About 620 also carried contact details, travel-document information, and KrisFlyer membership numbers | Reported | CNA |
| Star Flyer | Airline | Disclosed evidence of access to personal information and was still determining the number of affected customers at publication | Confirmed | Star Flyer |
| Asiana Airlines | Airline | Disclosed impact or potential impact without publishing an affected-customer count | Confirmed | Asiana Airlines |
| Malaysia Airlines | Airline | Named by CAAT among airlines affected through Amadeus. No affected-record count was published in the cited reporting | Reported | Nation Thailand |
| Thai Airways | Airline | About 60,529 passenger records may have been accessed. About 376 additional records may also contain passport numbers and contact details. Will contact affected passengers individually. Reported finding no disclosure of the data as of November 9 | Reported | Nation Thailand |
| Finnair | Airline | About 116,000 Finnair reservations appeared on flight lists involved in the breach, and roughly 750 were opened. Names Amadeus as data controller responsible for informing individuals, and will email customers whose contact details Amadeus supplies. Issued new reservation numbers for opened bookings which remained active | Confirmed | Finnair |
| SAS | Airline | Told IMY booking data for 350,164 travelers may have been exposed. Reporting on the notice states compromised system credentials enabled access followed by automated searches. Decided not to notify the travelers, judging the incident not high risk under the General Data Protection Regulation | Reported | Placera, SVT |
| Norwegian and Widerøe | Airline group | Reported 144,249 affected passengers to Datatilsynet and was still assessing whether individual notification was required | Reported | NordiskPost |
| Qantas | Airline | Was working with Amadeus to determine the impact on Qantas bookings. Reported its own systems and databases were unaffected | Reported | Information Age |
| Berg-Hansen | Travel agency | Named by NSM as a user of the affected Amadeus systems. Notified Datatilsynet of a breach connected to the incident | Reported | NSM, NordiskPost |
| Egencia | Corporate travel agency | Named by NSM as a user of the affected class of Amadeus systems. NSM did not identify Egencia as a confirmed victim in the cited notice | Confirmed | NSM |
| National Security Authority (NSM) | Government agency, Norway | States sensitive data leaked and Amadeus systems serve most of Norway's travel industry. Warns affected records can include identity, itinerary, passport, contact, seat, special-service, agency, and free-text information, and advises organizations to change log-in details at travel agencies and assess trips booked before September 23, 2026 | Confirmed | NSM |
| Civil Aviation Authority of Thailand (CAAT) | Aviation regulator | Identified six other Asian airlines affected through Amadeus and instructed Thai Airways to contact affected passengers promptly | Reported | Nation Thailand |
| Thai Ministry of Transport | Government ministry | Ordered aviation agencies and service providers holding personal data to tighten access controls, improve password management, and strengthen detection | Reported | Nation Thailand |
| Authority for Privacy Protection (IMY) | Data-protection regulator, Sweden | Received the SAS breach notification | Reported | Placera |
| Datatilsynet | Data-protection regulator, Norway | Received notifications from Norwegian and Berg-Hansen. Warned real travel details can make fraudulent messages more convincing | Reported | NordiskPost |
MITRE ATT&CK Mapping
| Tactic | Technique | Procedure | Status | Source |
|---|---|---|---|---|
| Initial Access | T1078, Valid Accounts | The threat actor accessed Amadeus booking data using credentials assigned to an Amadeus system account | Confirmed | Cathay Pacific, Korean Air |
| Persistence | T1078, Valid Accounts | The possible exposure window extends from August 10, 2023 through September 23, 2026, when Amadeus revoked the credentials. The public record does not show whether one account or credential set persisted throughout the period | Provisional | Nation Thailand |
| Collection | T1213.006, Data from Information Repositories: Databases | The threat actor accessed passenger booking records containing names, booking references, travel dates, routes, and cabin classes. Some records also held passport, nationality, contact, frequent-flyer, seat, and special-service data | Confirmed | ANA, NSM |
| Collection | T1119, Automated Collection | Reporting on the SAS regulatory notice states the threat actor performed automated searches after entering the booking system with compromised credentials | Reported | SVT |
Related Activity
The activity below provides technical and historical context for risk in shared airline-booking infrastructure. None of it was observed in the 2023 to 2026 credential-misuse incident, and its evidence remains separate.
| Activity | Relationship | Status | Source |
|---|---|---|---|
| Amadeus booking-display exposure, September 2026 | Heise reported an unauthenticated heap dump exposing plaintext credentials, authentication tokens, and administrator passwords associated with an Amadeus environment. Amadeus was alerted on September 21, 2026. Amadeus separately confirmed a vulnerability made booking-display data accessible and says it fixed the issue. Public reporting does not connect the exposed credentials to the system account used in the airline-record incident | Reported | Heise, Amadeus |
| Amadeus booking-system flaw, January 2019 | Researcher Noam Rotem found changing a page parameter exposed other customers' booking references across 141 airlines using the Amadeus online booking system. Amadeus fixed the flaw and reported finding no traveler-data breach | Reported | ITPro |
| SITA Horizon passenger-service breach, February 2021 | An intrusion at another passenger-service provider exposed frequent-flyer data held for multiple airlines. Singapore Airlines, Finnair, Malaysia Airlines, and Cathay Pacific later appeared in reporting on the Amadeus incident | Reported | TechCrunch |