What happened in the Railway security incident?
In its preliminary report, Railway says the attack ran from October 20 at 13:58 UTC to October 22 at 03:32 UTC. Engineers found a privilege escalation attempt in its build infrastructure, and the attacker went on to access credentials for Railway's CI environment.
Railway says the attacker pulled environment variables in encrypted form, and that an unauthorized query of encrypted variables led to a subset being decrypted with the compromised credentials. Railway can validate that at most 1.85% of workspaces, about 100,000, had some variables potentially compromised. It says the attacker did not log into user accounts, but it hasn't yet ruled out access to source code. Railway also revoked all Railway access tokens as a precaution and notified upstream providers so they could revoke keys.
Who is affected by the Railway breach?
- Workspaces with environment variables stored on Railway before October 21, 2026. Railway says at most 1.85% of workspaces had variables potentially compromised.
- Keys Railway reported to upstream providers. Railway says the group receiving provider reset requests was larger than 100,000 users because it notified broadly.
- Railway access tokens, which it revoked for everyone as a precaution.
How to check if you're affected
- Review GitHub audit logs and the access granted to installed apps, as Railway recommends.
- Review registry audit logs, such as Docker Hub, for pulls or pushes you don't recognize.
- Check the logs and billing of every service whose credentials lived in Railway variables, especially AI provider keys.
What to do now
- Revoke and reapply sensitive environment variables stored on Railway before October 21, and rotate the keys at each issuer.
- Roll private registry credentials.
- Remove public network access to databases that were reachable from Railway services.
- Contact support@railway.com with questions about your workspace.
What the Railway incident means for secrets stored in platforms
A deployment or AI platform that injects environment variables at runtime has to be able to decrypt them, so one compromise of its control plane or build system can expose every customer's keys at once. Treat platform-stored variables as copies of a credential, not as the credential's only home: keep an inventory of which keys live where, scope each key to the one service that needs it, set spend limits on AI provider keys, and make rotation a scripted step rather than a scramble. When a provider tells you to rotate, revoke the old key at the issuer, because deleting the variable from the platform doesn't invalidate it.
Where Nullify fits
How Nullify Covers This Class of Attack
Nullify finds credentials in code and verifies which ones still work with the provider that issued them (AWS, GCP, Azure, GitHub, GitLab, Stripe and Slack), so live keys rank first, then routes rotation to each owner. Rotation happens with the provider; Nullify doesn't rotate keys.
These secrets were stored in the platform, not in your code. Nullify's live-key check helps where the same keys also sit in your repositories or config.
Frequently Asked Questions
What happened in the Railway security incident?
An attacker escalated privileges in Railway's build infrastructure between October 20 and 22, 2026, accessed CI credentials, pulled encrypted environment variables and decrypted a subset. Railway says at most 1.85% of workspaces, about 100,000, had variables potentially compromised.
Do I need to rotate my Railway environment variables?
Railway recommends that all users revoke and reapply sensitive environment variables stored before October 21, 2026, and rotate those keys with the services that issued them. Deleting a variable doesn't invalidate the key, so rotation has to happen at the issuer.
Were Railway user accounts accessed?
Railway says the attacker did not log into user accounts. It revoked all Railway access tokens as a precaution and says it hasn't yet ruled out access to source code, which it will confirm in its final report.
Update Log
- Nov 17, 2026: page published from Railway's preliminary report.