# BrokenSesame: container escape and registry write access in a managed database service: the technique as the Wiz Research published it

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

Wiz Research published "BrokenSesame: container escape and registry write access in a managed database service" on 19 Apr 2023. 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:** 19 Apr 2023
- **Publisher:** Wiz Research
- **Access path:** [Cross-tenant access](/access-paths/cross-tenant/)
- **Source:** [the publisher's write-up](https://www.wiz.io/blog/brokensesame-accidental-write-permissions-to-private-registry-allowed-potential-r)

Wiz Research describes a container escape in two Alibaba Cloud PostgreSQL services, combined with registry credentials that also had write permission, which could reach other tenants' databases. The post says Alibaba Cloud confirmed the issues were fully mitigated and that no customer data was compromised.

## Related pages

- [Shared key authorization abused to escalate from storage t](/techniques/azure-shared-key-listkeys/)
- [SCARLETEEL: notebook containers exploited to steal cloud c](/techniques/scarleteel-fargate/)
- [A storage-account shared access token published with open-](/techniques/microsoft-ai-sas-token/)

## Sources

- BrokenSesame: container escape and registry write access in a managed database service: https://www.wiz.io/blog/brokensesame-accidental-write-permissions-to-private-registry-allowed-potential-r (read 16 Nov 2026)

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