# ChaosDB: Cosmos DB keys obtained from a notebook feature: the technique as the Wiz Research published it

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

Wiz Research published "ChaosDB: Cosmos DB keys obtained from a notebook feature" on 11 Nov 2021. 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. Read on 16 Nov 2026.

- **Published:** 11 Nov 2021
- **Publisher:** Wiz Research
- **Access path:** [Cross-tenant access](/access-paths/cross-tenant/)
- **Source:** [the publisher's write-up](https://www.wiz.io/blog/chaosdb-explained-azures-cosmos-db-vulnerability-walkthrough)

Wiz Research describes how a Jupyter Notebook feature in Azure Cosmos DB led to root privileges on a container and then to primary keys for other customers' databases. The post says the flaw was disclosed to Microsoft in August 2021 and gave access to databases of several thousand customers.

## Related pages

- [AutoWarp: another customer's tokens reachable from an auto](/techniques/autowarp/)
- [BingBang: multi-tenant apps that accept sign-ins from any ](/techniques/bingbang/)
- [BrokenSesame: container escape and registry write access i](/techniques/brokensesame/)

## Sources

- ChaosDB: Cosmos DB keys obtained from a notebook feature: https://www.wiz.io/blog/chaosdb-explained-azures-cosmos-db-vulnerability-walkthrough (read 16 Nov 2026)

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