Railway says customer secrets may have been exposed: rotate them now
On 21 Oct 2026 Railway said an unauthorized party may have accessed customer environment variables, some in decrypted form. Deployments are paused. Here is what to rotate and what to check.
Updated 11 Nov 2026: see what changedHow urgent
Act now
Who is affected
Anyone who stores API keys, database passwords or other secrets as environment variables on Railway
What to do
Rotate every secret stored in Railway now, starting with database passwords and keys for payment and AI providers, then check usage logs at each provider
Free checklist
Published 22 Oct 2026 · Sources last checked 11 Nov 2026No. 5 / 87
Updates, follow-ups and corrections
- Update · 11 Nov 2026. Railway has published its full incident report (updated 10 Nov, read directly). The attacker chained several exploits from 20 Oct. Railway says environment variables could have been decrypted for at most 1.85% of workspaces, about 100,000, an upper bound because its logs identify environments, not individual variables. It also says the attacker read the stored histories of 353 builds, sealed variables included, and decrypted linked-account tokens (BYOK agent keys and GitHub OAuth tokens) for 1,852 users. Unauthorized spend on the stolen keys is estimated at about $740,000; Railway is working with providers to refund it and asks customers to report charges they did not make. We have not seen a list of affected workspaces.
- Update · 27 Oct 2026. Railway has published a recovery guide (23 Oct). It is accepting deployments again, but commits pushed during the pause were not queued, so a service keeps running its last successful deployment until you trigger a new one. Railway revoked GitHub connections and API and CLI tokens, including project and account tokens. If builds fail, reconnect GitHub, check that the Railway GitHub app still has access to the repository, and recreate any CLI or CI token and update it in your CI secrets. The guide says nothing new about which accounts were affected or how the intruder got in.
We keep the original text. When something changes, when we follow a story, or when we get something wrong, we add a dated note here instead of editing silently.
What happened
On 21 October 2026 Railway, a cloud platform many small teams use to host apps and databases, published a security disclosure. The company says it detected unusual activity in the systems that store customers' environment variables. It believes an unauthorized third party may have accessed these variables and, for some of them, obtained the decrypted values.
Environment variables are the settings where many apps keep their secretsSecret (API key, token, password) Any piece of text that proves to a service that you are allowed in, such as an API key, a database password or an access token. Tap again to open the glossary: API keys, database passwords, private registry credentials. If you deploy on Railway, yours may be there.
Railway has paused deployments while it investigates, so new versions cannot roll out until builds are restored. It says it will email affected customers directly and update its status page as it narrows the scope.
Update, 11 November: the full report
On 10 November Railway published its full incident report. What it adds:
- How many. At most 1.85% of workspaces, about 100,000, could have had environment variables decrypted. Railway calls this an upper bound: the logs identify a set of environments, not individual variables. It emailed the customers at highest risk.
- How it happened, in Railway's words. The attacker chained several exploitsExploit A piece of code or a technique that takes advantage of a specific flaw to get something the attacker should not get. Tap again to open the glossary and moved between systems. In one step it used a short-lived credential to reach a machine that runs orchestration tasks, where a file on disk held a longer-lived credential able to decrypt stored variables. BleepingComputer's report describes the first step as a previously unknown flaw in Railway's build system that let the attacker escape its isolation.
- What else was read. The attacker read the stored histories of 353 builds, sealed variables included, and got a copy of internal source code, according to BleepingComputer.
- AI provider keys. The decrypted data included linked-account tokens, BYOK agent keys and GitHub OAuth tokens, for 1,852 users. Railway reset them all, notified those users and says it found no logins to Railway accounts using them.
- The bill. Unauthorized spend on the stolen keys is estimated at about $740,000. Railway says it is working with the providers to refund it and will cover it from its own balances for customers whose providers will not. It asks customers to report charges they did not make through its form.
- The timeline. The first exploit was at 07:28 UTC on 20 Oct and the attacker was evicted at 09:24 UTC on 21 Oct. Railway paused builds twice, invalidated every user session and token on 21 Oct, and restored builds for all plans by 22 Oct. It asked several providers, including GitHub, Anthropic, OpenAI and Google, to revoke potentially compromised keys.
- Agents on both sides. Railway describes the fight as "a contest of agent speed", and BleepingComputer reports that the attackers used AI-powered agents. We did not read Railway's full wording on this.
What we knew on 21 October, and what changed
- At first Railway believed the impact might be limited to a subset of customers and did not say how many. The 10 November report gives an upper bound of about 100,000 workspaces, still without a list.
- At first the company had not explained how the attacker got in. The full report now describes the chain of exploits above.
- Railway says it believes this is part of a recent series of attacks on platform companies, aimed at compromising AI inference providers. It says it has notified those upstream providers so they can revoke keys.
- Railway has also published follow-up posts on 22 October with checks for unusual access to AWS, GCP and GitHub, and for unexpected usage at services such as Stripe and AI providers. We have only seen the titles, so read them in full on Railway's blog.
What to do
Railway's own advice is to rotate everything and not wait to find out whether you were affected.
- Rotate every secret stored in Railway. Start with database passwords, then payment keys, then AI provider keys, then any private registry credentials. Revoke the old keys at each provider, not only in Railway.
- Check each provider's activity since 20 October. Look for calls from places you do not use, spikes in cost, new users or new keys. If you see charges you did not make, report them to Railway through its form and to the provider. Our key leak video walks through it: revoke, check usage, limit the damage.
- Set spending limits and alerts at your payment and AI providers, if you have not yet.
- Use the new values when builds resume. Because deployments are paused, your apps cannot pick up new values until Railway restores builds. Watch the status page.
- Keep a note of what you did and when. If customer data may have been involved, our incident plan explains who to tell and when.
If you build with AI tools
Our advice, not from the sources: if an AI tool deployed your app to Railway, ask it where your secrets live, and write the list down. Giving each key only the permissions it needs, and a spending cap, makes a leak like this far less costly. This is one more reason to treat every key as if it will leak someday.
Terms explained in this article
- Secret (API key, token, password): Any piece of text that proves to a service that you are allowed in, such as an API key, a database password or an access token.
Watch the short video
The video loads from YouTube (privacy-enhanced mode) only when you press play.
Comments
No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.
We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.
Sources and verification
- Railway blog: Security Disclosure, Wednesday October 21st (21 Oct 2026) (opens in a new tab)
- Railway status page: incident QH8L8B3E (build and deployment updates) (opens in a new tab)
- Cyber Security News: Railway security incident, hackers may have accessed customer environment variables (22 Oct 2026, press report) (opens in a new tab)
- Railway blog: Security Disclosure Recommendation, Recover Failing Deploys (23 Oct 2026) (opens in a new tab)
- Railway blog: Incident Report, October 21st Security Attack (updated 10 Nov 2026; read directly in a browser) (opens in a new tab)
- BleepingComputer: Railway breach leads to $740,000 in fraudulent AI charges (11 Nov 2026; read directly in a browser) (opens in a new tab)
We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.
Spotted a mistake? Email [email protected] and we will correct it and note the change.