Plataforma Railway · Breach

Railway confirms up to 100,000 workspaces with variables potentially exposed

Oct 20, 2026 · 1 min read

Railway, a hosting platform, suffered a breach between October 20 and 22, 2026 in which, per the company, an attacker sought AI provider keys and obtained decrypted customer environment variables; at most 1.85% of workspaces (about 100,000) were potentially affected. Attacker access ended October 22, builds and deployments were restored, and forensics remain ongoing. Anyone who signed up before October 21 should rotate all keys stored on the platform.

By HIFY Radar newsroom Updated 10/26/2026 01:20 PM Get this every day →← Back to the feed 3 sources

HighBreachNo software to update

In this article

What happened
Why it matters
What to do
For the technical team
Timeline
Sources

What happened

Railway, a hosting platform, reported an intrusion with attacker access to internal systems between October 20 and 22, 2026. Per the company, the goal was to obtain AI provider API keys; at most 1.85% of workspaces (about 100,000) had environment variables potentially compromised. Attacker access was terminated on October 22 and the forensic investigation is ongoing, with external experts and authorities engaged.

Why it matters

Environment variables often hold API keys and database and registry credentials, which could give third parties access to systems and data outside Railway. During the incident, builds and deployments were interrupted, with periods of dashboard, API, CLI and support unavailability. Railway itself says more than 100,000 users received key reset requests from providers.

What to do

Immediately rotate all keys and variables stored on Railway (recommended for anyone who signed up before October 21), revoke on GitHub the tokens used as registry credentials, review service and bucket logs, and redeploy services after the credential resets performed by Railway.

For the technical team

Affected: Plataforma Railway (variáveis de ambiente de projetos de clientes) · Customer projects with secrets stored as Railway environment variables. At most 1.85% of workspaces (about 100,000) had variables potentially compromised; Railway recommends rotation to everyone who signed up before October 21.
Exploitation: Exploitation confirmed by Railway itself, with attacker access window from October 20 13:58 UTC to October 22 03:32 UTC. Forensics indicate targeting of high-value workspaces: those with very many environment variables or many AI vendor keys. No CVE and no KEV; not a product flaw.
Fix: No patch (intrusion, not vulnerability). Mitigations: user session invalidation; Railway reset the S3 credentials (ACCESS_KEY_ID and SECRET_ACCESS_KEY) of every bucket in every environment, invalidated GitHub account connection tokens, and removed GitHub tokens stored as registry credentials on services; services need redeploy and GitHub must be reconnected manually. Customers must rotate all keys and revoke old ghcr.io tokens on GitHub.
Vector: Privilege escalation in Railway's build infrastructure by an external attacker, with parallel escalation across multiple parts of the system. The attacker queried encrypted environment variables from the database; then obtained CI environment credentials and decrypted artifacts holding additional API access, decrypting a subset of variables using a combination of compromised credentials. Per Railway, the target was AI provider keys for distillation attacks. Initial detection via abnormal latency alert on October 20, 13:58 UTC.
More details: Railway engaged external incident response experts and the authorities. It notified vendors (GitHub, GitLab, Anthropic, OpenAI, OpenRouter, SpaceXSI, Stripe and others) on October 21 at 09:25 UTC and, out of caution, provided some (GitHub, SpaceXSI) with all keys present on the platform, widening revocation notices beyond the 100,000 workspaces. The company says user accounts were not accessed and that access to source code is not ruled out until the final report. Per Railway, the attacker had access to 'abliterated' models and substantial compute resources. Discovered by Railway's own monitoring; covered by BleepingComputer and The Hacker News. Builds and deployments, paused during the incident, were fully restored on October 22 (17:00 to 22:49 UTC).