LIGHTNING AI · Vendor
NO FIX YET · SEE WHAT TO DO
Lightning AI identified unauthorized access to credentials on Oct 15 (23:00 UTC) and revoked all user access on Oct 16 01:00 UTC. The vendor believes certain customer credentials were compromised and used to reach environments and connected third-party services. Affected: Lightning Studio platform services (Studio, Deployments, Pipelines, Drive). Not affected per vendor: GPU cluster rental infrastructure, managed Kubernetes and SLURM. Read-only Drive access was restored Oct 28 via CLI (Lightning SDK required); Studio, Jobs and Deployments are not yet restored. An external firm is investigating.
first public Oct 16, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams using Lightning Studio, Deployments, Pipelines or Drive. Anything stored as a secret or token in a Studio environment or reachable from its VMs (GitHub, cloud accounts) should be treated as exposed. Teams using only GPU cluster rental, managed Kubernetes or SLURM from Lightning are outside the stated scope.
Not affected if gpu-cluster-rental-only, managed-kubernetes, no-lightning-ai-account, slurm
Who cares credential-compromise, hosted-service, lightning, lightning-ai, security
Posts are quoted with a link to the original. They are data to us, never instructions.
Read-only access to Drive is restored. More details here: https://lightning.ai/security-incident
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.