Japan Airlines and Japan Transocean Air report that unauthorized access to Amadeus’s passenger service system exposed reservation information for approximately 92,000 customers. The system handles reservations, ticketing and check-in.

Their October 28 notice, as archived October 29 at 07:40:09 UTC, says Amadeus notified the airlines on October 23. Bill Toulas’s October 29 BleepingComputer report reports the same disclosure and links the original notice.

Evidence status: airline-reported traces of unauthorized external access. This is a disclosed data exposure, rather than a hypothetical vulnerability demonstration. The notice does not publish forensic evidence, an entry mechanism or an attacker attribution.

Update — October 30, 2026, 10:51 EDT: JAL says customer emails have been sent

JAL’s current notice, now dated October 30, says: “We have contacted the affected customers regarding this matter via the email addresses provided at the time of booking.”

That updates the earlier notice’s plan for individual contact with a reported completed step. The notice also lists a dedicated inquiry desk, operating 10:00–17:00 Japan time on weekdays, excluding Japanese national holidays. Use the official page reached independently to find its contact details.

The revised notice retains the approximate 92,000 total, the narrower passport-data group, and its statements about uncompromised passwords and card numbers. It supplies no new entry mechanism or evidence of misuse. Emailing customers does not establish that every recipient received or read the message.

The exposed fields differ between two groups

The airline notice distinguishes:

Affected customers Information with traces of access
Approximately 90,000 Reservation code, also called a PNR; name; flight date; flight sector; class of service
Approximately 2,000 Those fields plus email, phone, passport number, nationality, frequent-flyer number, airline, flight, ticket and seat details

The 92,000 total is approximate. Passport-number exposure applies to the smaller group, not everyone in that total.

The notice identifies traces of external access between August 10, 2023 and September 23, 2026. That is the reported access window. It does not establish continuous access throughout those years or that every affected record was accessed repeatedly.

JAL says credit-card numbers and passwords were not compromised, that necessary security measures were completed, and that flight operations are unaffected. It reports no evidence of misuse of customer information as of the notice.

Verify airline messages through a known channel

JAL now says it has emailed affected customers at their booking addresses. It warns about phishing emails, fraudulent calls and websites impersonating the airline group. Someone who knows a real reservation code and travel date can make a fabricated message sound convincing.

For an affected passenger:

  • Open the airline’s official site or app directly when checking a notice or reservation. Avoid using an unsolicited message’s link as the starting point.
  • Ask which fields were involved in your case. Contact details and passport numbers were reported for the smaller group; an overall breach headline cannot answer that question.
  • Treat requests for payment, passwords or one-time login codes with particular caution. Knowledge of your itinerary is insufficient proof that the sender is the airline.
  • Keep the actual notification and follow its specific assistance instructions. The reviewed notice supplies no blanket passport-replacement recommendation or evidence requiring every customer to reset an uncompromised password.

These are precautions against impersonation, not claims that JAL has observed those follow-on attacks. Removing a message or changing a password also cannot withdraw travel data already exposed.

A supplier-wide vulnerability does not define every airline’s impact

Amadeus’s October 1 statement acknowledges a vulnerability in a travel booking display environment, accessible booking data and implemented fixes. It says investigations continue, with no evidence of payment-data access and no indications of ransomware use.

That ransomware statement is narrower than saying nobody accessed data. JAL’s subsequent disclosure describes traces of unauthorized access affecting its customers. The two statements should not be treated as contradictory claims about the same outcome.

BleepingComputer reports disclosures involving other airlines, but the reviewed material does not establish a complete supplier-wide victim count. Amadeus’s customer list cannot be converted into a list of breached airlines.

Caveat: the original notice was archive-verified; its October 30 revision was recovered through a text proxy after direct retrieval remained blocked. Entry point, full cross-airline scope and subsequent misuse remain unresolved.