Railway: build-infrastructure escalation exposed decrypted customer environment variables
Severity: critical · Patch status: patched · Since 2026-10-20
Railway, a cloud deployment platform with about 5 million users, disclosed that a targeted attacker escalated privileges in its build infrastructure on 20 October 2026, then pulled customer environment variables in encrypted form and decrypted a subset using compromised CI credentials. Railway estimates up to roughly 1.85% of workspaces (about 100,000) may be affected, but because it told vendors to revoke all stored keys for all users the revocation wave is wider. It says the attacker was hunting AI provider API keys for distillation, that user accounts were not accessed, and that running services stayed online; builds and deployments were paused and the attacker was cut off by about 03:32 UTC on 22 October. Source-code access is not yet ruled out, and the first-entry method is not disclosed. Separately, on-chain investigator tayvano alleges about $371,000 of crypto was drained from keys stored in Railway; Railway has not confirmed this. Wiz counts it among at least nine AI developer platforms breached in October 2026.
What to do
- Rotate every secret stored in Railway environment variables (AI provider keys, database credentials, private registry credentials, cloud keys), especially anything created before 2026-10-21, revoking at the issuer first
- Private keys or wallet seeds kept in Railway should be treated as burned: move funds to new addresses
- Remove public network access to databases; review GitHub audit logs and installed GitHub App access, and registry (for example Docker Hub) activity logs
- Reconnect GitHub, recreate CLI and CI tokens (all Railway tokens were revoked), and redeploy the latest commit since pushes during the pause were not deployed
- Check AI provider and cloud billing for fraudulent usage; Railway cannot refund spend made with leaked keys, so contact the provider first
Sources
All live incidents on Threat Watch
