SAS.
DATA BREACH
SAS (transport, Sweden) was hit by a data breach first reported on 10 November 2026. No group has been publicly named as behind it in these reports. 437 news reports in the last 14 days, 0 in the last 24 hours; the latest, from teiss: “Personal data of over 350,000 SAS passengers compromised in Amadeus incident”. See every attack on the live map.
What happened in the SAS data breach
Scandinavian Airlines (SAS), the Swedish-based airline, reported a suspected data breach affecting 350,164 people. The leak sits in Amadeus, the Spain-based travel technology provider that runs the reservation system SAS uses. SVT Nyheter first reported the filing to Sweden's privacy regulator, IMY, on 9 November 2026, and The Local and others followed. Nobody has been named as the attacker.
Amadeus disclosed in October 2026 that it had detected unusual activity in September 2026 and had alerted airline partners. SAS says the access may have covered August 2023 to September 2026. Norway's National Security Authority (NSM) said the vulnerability was closed on 23 September 2026 and that an unauthorised actor may have had access for at least three years. The breach also reaches Finnair, Norwegian, Widerøe, Berg-Hansen and several Asian and Australian carriers.
SAS told IMY that the exposed data mainly covers booking administration and travel information, mostly for older bookings and completed trips. SAS says no other categories of personal data have been identified so far. SAS has decided not to notify passengers individually because it does not consider the breach high risk under GDPR, though it says that view could change if new information emerges.
An external actor is believed to have used compromised system credentials to reach the Amadeus booking system and run automated searches, according to SVT as cited by other outlets. Amadeus is investigating and says it has fixed the vulnerability and strengthened monitoring. It says there is no evidence so far that payment or financial data was accessed.
The investigation into the scale of the breach remains open. Norwegian reporting by NRK says passport details may have been accessible in some cases, and NSM has said passport numbers could be among the wider Amadeus data depending on the booking.
- What was taken: According to SAS, the exposed information includes booking references, travel dates, the number of passengers in a booking and flight-related details. SAS says it has not identified other categories of personal data. Amadeus says card numbers and passwords were not exposed. NRK reported that passport details may have been accessible in some cases, and NSM said passport numbers could be among the wider data depending on the booking.
- Who is affected: SAS told IMY that 350,164 people may be affected. Finnair says about 116,000 of its reservations were affected, which is a different measure and cannot be added to the SAS total. Amadeus is examining 750 SAS reservations, according to Nordisk Post. Norwegian and Widerøe have separately reported 144,249 travellers, according to a notification sent to Norway's data protection authority. Reports say the affected passengers include people in Sweden, Denmark, Spain and Norway, according to NRK as cited by SMP.
- Who is behind it: Nobody has been publicly named or has claimed the attack. SVT, as cited by Nordisk Post, says an external actor is believed to have used compromised system credentials to access the Amadeus booking system.
- The response: SAS said it is aware of the security incident reported by Amadeus and has informed the relevant supervisory authorities. It told IMY that it has decided not to notify affected passengers individually, saying it does not consider the breach high risk under GDPR, and that this could be reviewed if new information emerges. Amadeus says it has fixed the vulnerability, enhanced its monitoring and is continuing its investigation. Amadeus is also reported to have assigned new reference numbers to some still-active bookings to prevent unauthorised access. In Norway, NSM said it had received a concern from the travel agency Berg-Hansen on 27 October 2026 and has informed Norwegian organisations so they can take steps to reduce risk.
Was my data taken in the SAS data breach?
For this data breach: SAS has not contacted affected passengers directly, so you may not receive a notice about this breach. Watch for updates from SAS and from the Swedish Authority for Privacy Protection (IMY) in case the company changes its position. If you are concerned about your data, you can write to Amadeus through its data protection address, which Deeparrival says is available. Be cautious with unexpected messages that mention your trip or booking.
Only SAS can confirm whose data was involved. If you are a customer, these five steps cover you either way:
- Look for an email or letter from SAS. Firms whose data is taken usually have to tell the people affected, and it says what was taken.
- If you have an account with SAS, change its password, and the password anywhere else you used the same one.
- Turn on two-step sign-in where you can, so a stolen password is not enough on its own.
- Expect scam emails, texts and calls that mention SAS or this breach. Do not click links in them; go to the real website yourself.
- Check whether your email address has turned up in known breaches at haveibeenpwned.com. In the UK, report money lost to fraud to Action Fraud.
SAS data breach: the details
- Type: Data breach
- Sector: Transport
- Where: Sweden
- Reports, last 14 days: 437
- Latest report: 10:57 UTC, 12 November 2026
See the numbers
| Day | Reports |
|---|---|
| 3 Nov | 0 |
| 4 Nov | 0 |
| 5 Nov | 0 |
| 6 Nov | 0 |
| 7 Nov | 0 |
| 8 Nov | 0 |
| 9 Nov | 0 |
| 10 Nov | 436 |
| 11 Nov | 0 |
| 12 Nov | 1 |
| 13 Nov | 0 |
| 14 Nov | 0 |
| 15 Nov | 0 |
| 16 Nov (so far) | 0 |
Latest SAS news
- Personal data of over 350,000 SAS passengers compromised in Amadeus incidentteiss · Data breach · Sweden · 12 Nov 2026, 10:57 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
Earlier reports
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Stockholm, Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Stockholm, Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Stockholm, Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Stockholm, Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Place unknown · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Stockholm, Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
- 350,000 SAS passengers may have had details leaked in major data breachThe Local Europe · Data breach · Sweden · 10 Nov 2026, 09:00 UTC
Showing the latest 100 of 437 reports. See every report in the live map.
SAS data breach: timeline
- 2026-09-23: NSM says the Amadeus vulnerability was closed on this date, according to Nordisk Post reporting.
- 2026-10-27: NSM received a concern from the travel agency Berg-Hansen about the security incident, according to NRK as cited by SMP.
- 2026-11-09: SVT reported that SAS had notified the Swedish Data Protection Authority (IMY) of the suspected breach, and the story became public.
- 2026-11-10: The Local reported that SAS had confirmed the breach to SVT and that 350,164 people may be affected.
- 2026-11-13: Nordisk Post reported a separate Norwegian and Widerøe notification affecting 144,249 travellers from the same Amadeus breach.
Sources for the story
- teiss - News - Personal data of over 350,000 SAS passengers compromised in Amadeus incident
- 350,000 SAS passengers may have had details leaked in major data breach
- SAS Data Breach May Affect 350164 Travellers
- SAS reports suspected breach affecting 350,000 passengers - Daily Northern
- SAS data breach at Amadeus affects 350,000 travellers
- Norwegian and Widerøe data breach affects 144,249 travellers
- Opplysninger om 350.000 SAS-passasjerer lekket
- Opplysninger om 350.000 SAS-passasjerer lekket - smp.no
- SAS rammet av datalekkasje: Berører 350 000
- Jätteläcka: Implications for Travelers Everywhere - Svenska magasinet
SAS data breach: common questions
What happened to SAS?
SAS (transport, Sweden) was hit by a data breach first reported on 10 November 2026. No group has been publicly named as behind it in these reports.
Was my SAS booking data stolen?
SAS says certain booking information linked to the airline has been affected and that 350,164 people may be affected. Not all of those people may have had data taken, as SAS describes the incident as a possible exposure.
Did SAS tell passengers about the breach?
SAS has not notified affected passengers individually. It says it does not consider the breach high risk under GDPR, but that this decision could change if new information comes to light.
Were passport numbers or payment cards exposed?
SAS says no categories of personal data beyond booking details have been identified. Amadeus says card numbers and passwords were not exposed, and NRK reported that passport details may have been accessible in some cases.
Who is behind the attack?
Nobody has been publicly named. SVT reports that an external actor is believed to have used compromised system credentials to access the Amadeus booking system.
How long was the data accessible?
SAS says the access may have covered August 2023 to September 2026, and NSM says an unauthorised actor may have had access for at least three years. The investigation into the scale of the breach remains open.
Who is behind the SAS data breach?
No group has been publicly named in the reports collected here. Attribution can take weeks and is often disputed.
Was my data affected?
Only SAS can say whose data was involved; its own statement is usually linked from the latest reports below. If you are a customer, watch for emails or texts that mention the breach, change your password there and anywhere you reuse it, and turn on two-step sign-in.