Railway breach: rotate every secret stored before October 21
The Railway breach exposed environment variables for up to 1.85% of workspaces. The attacker wanted AI API keys. Here is the rotation list and what to change.
If you deploy on Railway, stop reading after this sentence and go rotate your keys. The Railway breach disclosed on October 21 let an attacker query encrypted customer environment variables and decrypt a subset of them. Railway's preliminary report says the target was AI provider API keys. Your OpenAI, Anthropic and OpenRouter keys were the prize, and your Stripe and database credentials were in the same file.
What actually happened
From Railway's own timeline (UTC):
- Oct 20, 13:58: On-call was paged for elevated latency. Railway marks this as the start of the attack window. Engineers found a possible privilege escalation in build infrastructure and halted builds.
- Oct 21, 05:27 to 09:18: The attacker reached CI credentials, then ran unauthorized queries against encrypted environment variables. A subset was decrypted.
- Oct 21, 09:25: Railway asked vendors, including GitHub, GitLab, Anthropic, OpenAI, OpenRouter and Stripe, to revoke exposed keys.
- Oct 22, 03:32: Railway confirmed the attacker no longer had access. Full API and deploys were back by that evening.
Railway says at most 1.85% of workspaces, about 100,000, had some variables potentially compromised. Running deployments stayed up. User accounts were not accessed, but source code access is not yet ruled out. That answer waits for the final report. TechCrunch reports Railway still told all users to rotate, and has not named a root cause.
Why the Railway breach matters for your business
Your PaaS is a key vault, whether you planned it or not. Most small teams paste every secret into the host's env panel. One platform compromise then hands out your payment processor, your database and your AI spend in one query. Railway flagged two high-risk profiles: workspaces with lots of variables and environments with lots of AI keys. That describes most AI products we see.
AI keys are now cash. A stolen model key does not leak data quietly. It runs up your bill, or gets resold for someone else's distillation run. Set hard spend caps and usage alerts with every model vendor today.
Rotation is a drill, not a crisis. If rotating means hunting through five dashboards at midnight, your secrets have no owner. Keep a list of every key, where it lives and who can reissue it.
Key takeaways
- Railway says an attacker decrypted a subset of environment variables between October 20 and 21
- Up to 1.85% of workspaces, about 100,000, were potentially exposed; the target was AI API keys
- Rotate every variable stored before October 21, including private registry credentials
- Remove public network access to databases and check GitHub and Docker Hub audit logs
- Put spend caps on every AI provider key and keep a written rotation list
Not sure which keys your apps hold, or where? We map your secrets, move them into a manager you control, and set caps and alerts on your AI spend, so the next platform breach costs you an afternoon, not a month. Ask us for a secrets review, or see how we build.
Sources: Railway: Preliminary Report, October 21 Security Incident, Railway Security Disclosure, TechCrunch.
- #railway
- #security breach
- #api keys
- #secrets management
- #environment variables
Tommy Rush — Founder, Rush Commerce
Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More
Get The Rush Report weekly — one email, zero fluff.
Keep reading
Nextcloud Collabora CVE-2026-110447: update or remove the app
CISA lists CVE-2026-110447 in Nextcloud's built-in Collabora CODE app as exploited. Update richdocumentscode to 26.4.303 or remove it, then hunt for web shells.
Read itApple multiseat subscriptions are on by default: check your app
Apple now sells app subscriptions in bulk through Apple Business and School Manager, and multiseat is on by default. What changed and what your backend must handle.
Read it