Skip to main content
Skip to content

Breach Watch

Amadeus — Exploited vulnerability

This record covers the exploitation of a vulnerability at Amadeus.

The sources for this record do not confirm how many people were affected and when the incident happened.

  • Exploited vulnerability
  • Reported
  • Public record: 2 November 2026

What matters

Who was affected
Not stated
People affected
Not stated
Information involved
Booking-display data
Authorities notified
Australian Cyber Security Centre

Key dates

Incident date
Not confirmed
Discovery date
Not confirmed
Disclosure date
Not confirmed
Notification date
Not confirmed
Public record
2 November 2026

Each date is either established by a quoted source or explicitly not confirmed. The public record date is when the incident was first publicly reported, not when it occurred.

Affected people and data

Categories of affected data

Other information
  • booking-display data

Grouped by Cleverer for reading. Each item is worded as the source states it.

Notifications and response

Government cyber security agencies notified

  • Australian Cyber Security Centre

What the organisation says it did

  • notified the Australian Cyber Security Centre

Not stated: Regulators notified · Police notified · Remediation stated

Sources

Each source is labelled by what it is: the organisation's own statement, a regulator's publication, or a news report. Follow the link to read the original.

Original report

Qantas among several airlines probing data breach and customer booking impacts after Amadeus cyber attack | 7NEWS

7news.com.auRetrieved 3 November 2026

For people who may be affected

If you may be affected

This record does not yet cite a notice from Amadeus with instructions for affected people. If you have been told you are affected, follow the instructions in that notice, and reach the organisation through contact details on its own website.

Practical steps

  1. Treat unexpected calls, texts and emails that mention this incident with caution. Contact the organisation using details you find yourself, not details in the message.
  2. Keep a note of any notice you receive and anything you do in response. It helps if you need to make a complaint or claim later.

Official help

Cleverer is not connected with Amadeus and cannot tell you whether your information was involved. Only the organisation can confirm that.

For Australian businesses

What would your business need to prove after an incident like this?

This record is classed as exploited vulnerability. Incidents of that kind raise questions any business holding personal information should be able to answer with records, not recollection. This is not a finding about the organisation in this record. It is what another business would want on file if the same thing happened to it.

  1. An asset register

    Showing which systems you run and which of them face the internet.

  2. Vulnerability and patch records

    Showing when you learned of a flaw, and when you fixed it.

  3. Monitoring and alert records

    Showing how you would notice unusual access, and what happened when you did.

  4. Supplier responsibility records

    Showing who was responsible for patching each hosted or managed system.

  5. Notification decision records

    Showing how you assessed whether the breach was notifiable, and when you decided.

Could your business prove what it had in place?

A policy shows what you intended. Evidence shows what happened. Check your current cyber compliance position and see which evidence is missing.

Cleverer helps businesses keep this work current and retain dated evidence of what was actually done. It does not prevent breaches, and nothing on this page is a finding about how this incident happened or what the organisation in this record did.

© 2026 Cleverer. Human-layer cyber compliance for Australian businesses.