Cyber & AI intelligence
Briefs indexed3754
Issues36
Published Mondays07:30 CT
▣ Breach CARIBBEAN-AIRLINES 2026-11-16

Caribbean Airlines: Passenger Booking Data Exposed Through Amadeus Supplier Breach

"Caribbean Airlines (CAL), Trinidad and Tobago's state airline, has publicly confirmed that an unauthorised party accessed passengers' booking and reservation records held by its reservations technology provider, Amadeus…"

Caribbean Airlines (CAL), Trinidad and Tobago's state airline, has publicly confirmed that an unauthorised party accessed passengers' booking and reservation records held by its reservations technology provider, Amadeus IT Group. The airline issued its public statement on Sunday, 15 November 2026. That was ten days after the 5 November date given in its own customer emails, and two days after it began quietly emailing affected passengers on 13 November. CAL has not said how many of its passengers are affected. It says preliminary information from Amadeus suggests no payment card data was accessed, and its investigation is still ongoing. The incident is the latest Caribbean case in a supplier breach that has already hit Japan Airlines, All Nippon Airways, Cathay Pacific, Thai Airways, Finnair and several other carriers.

What Happened

The Trinidad Guardian first reported the incident on 14 November. It cited an email sent to affected passengers on 13 November that said: "On 5 November 2026, Caribbean Airlines was informed that an unauthorised party gained access to certain reservation information through a compromised system account." That email did not name the supplier. Guardian Media reported that CAL's reservation and booking system is run by Amadeus, and CAL's later public release confirmed this.

A CAL official confirmed the breach to the Guardian on 13 November but would not give more detail, citing the investigation. The official said the airline was contacting affected passengers only. According to Guardian Media, the paper was told that data protection laws in several of the countries where CAL operates required the airline to announce the breach publicly. After the Sunday Guardian reported that the airline had told only the customers it had identified, CAL published a release on 15 November confirming the incident.

The dates do not line up, and readers should not treat 5 November as the date the intrusion happened:

If CAL's records were exposed in the same Amadeus intrusion, they could have been readable for much of that period of roughly three years. CAL has not said when its own records were first accessed.

The questions about how CAL handled disclosure remain open. Transport and Civil Aviation Minister Eli Zakour did not respond to Guardian Media's questions about when he was told of the breach and whether he was satisfied that CAL had met its legal obligations. CAL chairman Reyna Kowlessar referred questions to acting chief executive Varma Khillawan. The Guardian contrasted CAL with the other affected airlines, which it says disclosed publicly and gave the number of customers affected. Antigua News Room noted that CAL has not said whether passengers travelling to or from Antigua and Barbuda are among those affected.

What Was Taken

CAL has not published a count of affected passengers or a definitive list of exposed data. Its customer email says the airline does "not yet have all the information necessary to confirm the precise data elements" in each record. It says exposed information "may include reservation-related details such as your name, booking reference, travel itinerary, contact information, and other information contained in your booking record," and adds that not every record contains the same fields.

The public release says preliminary data from Amadeus suggests no payment card data was accessed and that the breach was "limited to passengers' booking or travel data." The airline also says it has no evidence so far that the information has been misused.

Disclosures by other carriers show what an Amadeus booking record can hold. Japan Airlines, as reported by BleepingComputer, said:

BleepingComputer puts JAL's total at about 92,000. Cyberpresso cites "about 90,000," which matches JAL's main group but leaves out the smaller group whose passport and contact details were also exposed. Cyberpresso also reports these figures for other airlines:

These figures describe other airlines only. They are not estimates for CAL. They show that the exposure usually splits into a large group with basic itinerary data and a smaller group with identity-document and contact details. CAL has not said which group its passengers fall into.

The list of affected airlines also differs between accounts. CAL's release names Japan Airlines, Singapore Airlines, Cathay Pacific, Finnair, Thai Airways, Korean Air and Qantas. Cyberpresso, writing on 9 November, adds ANA, Asiana and Malaysia Airlines. It also says Qantas was still working out whether its bookings had been hit. We have not found a Qantas statement confirming that it was affected.

Why It Matters

One supplier, many victims. BleepingComputer reports that Amadeus serves more than 400 airlines, 210 airport operators, 34 cruise and ferry lines and 2 million hotels. A single account with access to Amadeus systems has now led to separate breach notices from airlines in Asia, Europe, Australia and the Caribbean. CAL's own network was not the entry point, but the data belongs to its passengers. That gap between where the breach happened and who owns the data is the theme of analyst Raéd Alexander Ayyad's two-part series, "The Airline Wasn't Breached. Its Passengers' Data Was."

Disclosure delays. CAL's sequence ran like this:

  1. 5 November: CAL was informed of the breach.
  2. 13 November: CAL began emailing passengers it had identified.
  3. 15 November: CAL made a public statement, after press coverage.

That timeline is likely to draw regulatory attention in the countries CAL serves, especially since its larger peers published passenger counts.

Phishing using exposed bookings. Booking references, itineraries and contact details are enough to write convincing messages about flight changes, rebooking or refunds. CAL has told passengers to watch for suspicious emails, messages and calls about their travel. Finnair took a stronger step: Cyberpresso reports that it issued new booking numbers for active reservations so the old codes cannot be used to access trips.

Long, undetected access. If the August 2023 start date reported by JAL and Thai Airways is correct, someone had access for about three years before it was found. The core problem is detection, not just patching.

The Attack Technique

The accounts describe the cause in two different ways:

These two descriptions can both be true. For example, a flaw in the display environment could have let a valid service account see records it should not have been able to see. Neither Amadeus nor CAL has said publicly how the two fit together. No threat actor has been named, and nobody has publicly claimed responsibility. Amadeus has told The Record, as cited by Cyberpresso, that it has seen no sign of ransomware. CAL and Antigua News Room report that Amadeus has since fixed the vulnerability and improved its monitoring and detection.

Ayyad's analysis focuses on non-human identities such as service accounts, API keys and application credentials. These accounts run all the time and rarely draw scrutiny, so misuse can blend in with normal traffic. In his words: "A compromised credential should not automatically become an invisible credential."

What Organizations Should Do

  1. List every supplier that holds your customer data and confirm how you will be notified. CAL's customer email did not name Amadeus, and its first notice went only to selected passengers. Contracts should require suppliers to report incidents quickly and in detail, including the period of access, which records were affected and which data fields were involved. That is the information you need to meet your own disclosure deadlines in each country where you operate.
  2. Treat service accounts as privileged identities. Keep an inventory of service accounts and API credentials on shared platforms. Give each one only the access it needs, rotate credentials on a schedule, and remove accounts nobody owns.
  3. Watch how service accounts behave. Set a normal baseline for how much data each account reads and which records it touches. Alert on bulk or unusual reads of reservation records, such as reads of flight lists or customer records outside the account's usual work. Access that lasts three years is a detection failure.
  4. Make exposed booking codes useless. Follow Finnair's example: reissue booking references for active reservations, and require a second check before anyone can change bookings, issue refunds or update contact details.
  5. Warn customers about phishing before attackers send it. Tell affected customers exactly which fields were exposed, how you will and will not contact them, and how to verify a message about their booking. Prepare your support teams for rebooking and refund scams.
  6. Prepare public disclosure in parallel with customer notification. Plan for regulators and the press to learn about the incident at the same time as customers. Publish a statement with the known scope, including passenger counts when you have them, instead of waiting for coverage to force one.

Sources: CAL confirms data breach; says investigation ongoing - Trinidad Gua... | Japan Airlines suffers third-party data breach exposing passenger info | Worrying data breach at CAL - Trinidad Guardian | Caribbean Airlines confirms data breach affecting passengers’ booki... | Worrying data breach at CAL - Trinidad Tribune – Latest Trinidad An... | CAL confirms data breach; says investigation ongoing - Trinidad Tri... | An Intruder Read Airline Bookings Inside Amadeus | The Airline Wasn't Breached. Its Passengers' Data Was PART II. THE...