Railway breach exposes environment variables and AI keys across 100,000 workspaces
A recent Railway security incident allowed an attacker to decrypt customer environment variables across up to 100,000 workspaces. The incident involved chaining a build isolation escape with an OIDC misconfiguration, leading to a targeted breach of AI provider credentials and other sensitive keys. The attacker stole credentials linked to AI, cloud, database, and payment services, resulting in approximately $740,000 in unauthorized token spend. Railway responded by revoking credentials, halting builds, and enhancing security controls. No customer source code or databases were accessed, but the incident underscores the risks associated with shared build environments and credential management.
Entenda a falha
A vulnerabilidade
Railway has no CVE for this. The articles describe a chain of weaknesses in its platform: an unspecified flaw in the multi-tenant build infrastructure that let the attacker partly escape filesystem isolation, a build credential that the internal Temporal cluster trusted beyond its intended use, and an erroneously defined OIDC binding in a cloud environment. The attacker needed no customer interaction, only the ability to run builds (the articles do not say how). The result was decryption of customer environment variables for up to 100,000 workspaces (at most 1.85%). Affected and fixed versions do not apply, since this is a hosted service. Railway patched the builder and revoked credentials on October 20 and 21, 2026.
Como funciona
On October 20, 2026, the attacker partly escaped filesystem isolation in the multi-tenant build infrastructure, read files on the host virtual machine and stole an internal build credential. That credential was meant only for image registry pushes, but the internal self-hosted Temporal cluster accepted it as a trusted client. Through a Temporal API the attacker pulled build histories and a cached snapshot of the internal monorepo. On October 21, the attacker found the misdefined OIDC binding in the stolen source and used it to get short-lived cloud credentials. With those, the attacker took an internal SSH key and reached a fleet orchestration machine in an internal VPC. That machine held a longer-lived credential used to decrypt envelope-encrypted customer variables, so the attacker queried the production database and had the key management service decrypt the matching keys.
Por que é vulnerável
The causes were weak isolation and over-broad trust. Build isolation in the shared build environment could be partly escaped, and the articles do not give the root cause of that flaw. A build credential meant for registry pushes was accepted by Temporal as a trusted client, and an OIDC binding was configured wrongly. A long-lived decryption credential also sat on disk on an orchestration host. The fix moves every build into a dedicated ephemeral virtual machine, rebuilds the internal CI/CD pipelines, restricts key decryption to the secrets service and enforces biometric and two-factor authentication controls.
Como foi descoberta
Per Railway's post-mortem, as relayed by SecurityOnline, forensic investigation reconstructed the intrusion, which began with dummy account probing on October 18, 2026. The unauthorized access ran from October 20 to 21 and was contained when Railway revoked credentials and patched the builder. Railway believes the attacker targeted AI provider credentials to sell. The incident resembles other AI credential thefts that Wiz's 'Black October' research tracked, and Railway cited Wiz regarding a harness similar to ARTEX. The articles do not say how the build isolation flaw itself was identified. Railway filed a complaint with the FBI's IC3 and hired an external forensics firm.
Explicação gerada por IA a partir da matéria e dos artigos, em 11/11/2026 11:15.
Linha do tempo
-
Railway breach exposes environment variables and AI keys across 100,000 workspaces
ler a análise desta fonte ocultar
A recent Railway security incident allowed an attacker to decrypt customer environment variables across up to 100,000 workspaces. The incident involved chaining a build isolation escape with an OIDC misconfiguration, leading to a targeted breach of AI provider credentials and other sensitive keys. The attacker stole credentials linked to AI, cloud, database, and payment services, resulting in approximately $740,000 in unauthorized token spend. Railway responded by revoking credentials, halting builds, and enhancing security controls. No customer source code or databases were accessed, but the incident underscores the risks associated with shared build environments and credential management.