Skip to content
Recent security issue
1985ml
OP

5 days ago

Hi, I haven't really been following the recent security issue on Railway so wanted to check if I have been impacted and what I should be doing?

Thanks!

Awaiting User Response

1 Reply

Status changed to Awaiting Railway Response Railway • 5 days ago


5 days ago

We're sorry for the worry this causes. On October 21, 2026 we had a security incident in which an attacker could access customer environment variables, and the final report confirms that access ended at 09:25 UTC that day. We can't give a workspace-specific answer on which variables, if any, were accessed, so the recommended precaution is to rotate any sensitive credentials (API keys, database passwords, tokens) that were stored in Railway before that time, update the variables, redeploy the services that use them, and review your providers' activity and audit logs, especially for AI provider keys.

Credentials you create and store after 09:25 UTC on October 21 were not exposed through this incident and are safe to store on Railway. If you use a Railway Postgres database, you can rotate its password with Regenerate under the database's Config > Connection settings, which updates the variables for you.

The full details are in our final incident report.


Status changed to Awaiting User Response brody • 5 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...