Get started

Data breach, reported Oct 20, 2026

CSX data breach

CSX sent notices of a data breach on Oct 20, 2026, according to the Indiana and Vermont attorneys general. Indiana lists 39,313 people affected in total and a breach date of May 29, 2026. Vermont lists Social Security numbers, government ID numbers, financial account codes and credit and debit account information as involved.

Reported
Oct 20, 2026
Breach began
May 29, 2026
People affected
39,313 (Indiana filing)

Key facts

Data exposed
Social Security numbers, government ID numbers, financial account codes, and credit and debit account information (Vermont filing)
States notified
Indiana and Vermont

What happened

The Indiana Attorney General lists a breach notice from CSX dated Oct 20, 2026, with a breach date of May 29, 2026. That is a little under five months between the breach and the notices. The Vermont Attorney General lists a notice from CSX on the same day.

Neither list describes how the breach happened, how CSX found it or what it did in response. Claim did not find a published notice letter for this breach on the state lists it reads as of Nov 16, 2026. The letter mailed to each person is the company's own account of the incident and should be kept.

What information was exposed

The Vermont list shows these categories of data for the residents notified there:

  • Social Security numbers.
  • Government ID numbers.
  • Financial account codes.
  • Credit and debit account information.

The Indiana report does not list data types. Your letter says which items applied to you.

Who was notified

  • Total affected: 39,313 (Indiana filing).
  • Indiana residents: 2,511.
  • Vermont residents: 9.

Claim did not find this breach on the California, Washington, Oregon or Texas lists or on the HHS breach portal as of Nov 16, 2026. Those lists may add it later, since filings often arrive at different times.

What CSX is offering

The state lists do not say whether CSX is offering credit monitoring or identity protection. Check your letter for any offer, the enrollment code and deadline, and a phone number for questions.

What to do now

  • Place a free credit freeze with Equifax, Experian and TransUnion and ask the IRS for an Identity Protection PIN at irs.gov/ippin.
  • Call your bank and card issuers if your letter lists account or card details. Ask for new numbers and set up transaction alerts.
  • Watch for accounts opened with your government ID number, such as a driver's license or passport.
  • Get free credit reports at annualcreditreport.com and report identity theft at IdentityTheft.gov.

Lawsuits and settlements

As of Nov 16, 2026, no settlement has been announced for the CSX data breach in the sources Claim reviewed. Claim tracks new data breach settlements and lists them when they open.

Frequently asked questions

Is the CSX breach letter real?

The Indiana and Vermont attorneys general both list a breach notice from CSX dated Oct 20, 2026. To confirm a letter, call CSX at a number you find on its own website, not only the number in the letter.

Was I affected?

Indiana lists 39,313 people affected but does not name them. People whose information was involved should have received a letter around Oct 20, 2026.

Will there be a CSX settlement?

No settlement had been announced as of Nov 16, 2026, in the sources Claim reviewed. Claim tracks new data breach settlements and can alert you if one opens.

What should I do if my Social Security number was exposed?

Freeze your credit at Equifax, Experian and TransUnion, ask the IRS for an Identity Protection PIN, and check your credit reports for accounts you did not open. Report misuse at IdentityTheft.gov.

Claim finds settlements you qualify for and helps you file.

Get alerts if a settlement opens

Related pages

Last updated Nov 17, 2026 by Dev Dixit, Head of Media at Claim. Claim works to keep these details accurate. If this page differs from an official source, the official source is correct.

Claim is not a law firm, a court, a government agency, or a settlement administrator, and does not give legal advice.

This page is a plain language summary, not legal advice, and does not create an attorney client relationship.

Company names are trademarks of their owners. Claim uses them only to identify the matter described on this page and is not affiliated with those companies.

Read our full disclaimer