# AutoWarp: another customer's tokens reachable from an automation service: the technique as the Orca Security research published it

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

Orca Security research published "AutoWarp: another customer's tokens reachable from an automation service" on 7 Mar 2022. The ledger files it under cross-tenant access. It is a disclosed research technique, not an incident. The source is the publisher's own write-up.

- **Published:** 7 Mar 2022
- **Publisher:** Orca Security research
- **Access path:** [Cross-tenant access](/access-paths/cross-tenant/)
- **Source:** [the publisher's write-up](https://orca.security/resources/blog/autowarp-microsoft-azure-automation-service-vulnerability/)

Orca's research reports a flaw in Azure Automation that let it reach an internal server managing other customers' sandboxes and obtain authentication tokens for their accounts. The post gives a timeline with discovery on 6 December 2021, a fix on 10 December 2021 and public release on 7 March 2022.

## Related pages

- [BingBang: multi-tenant apps that accept sign-ins from any ](/techniques/bingbang/)
- [BrokenSesame: container escape and registry write access i](/techniques/brokensesame/)
- [Shared key authorization abused to escalate from storage t](/techniques/azure-shared-key-listkeys/)

## Sources

- AutoWarp: another customer's tokens reachable from an automation service: https://orca.security/resources/blog/autowarp-microsoft-azure-automation-service-vulnerability/ (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecuritybreaches.com/techniques/autowarp/
