Masked namespace vulnerability in Temporal(depthfirst.com)

32 pointsby bmit5 mesi fa4 comments

Masked namespace vulnerability in Temporal

https://depthfirst.com/post/the-masked-namespace-vulnerability-in-temporal-cve-2025-14986

4 comments

haneul5 mesi fa

Even in a product as technically wonderful as Temporal, we can have relatively simple oversights like this that lead to cross tenant leakage.

If anyone is more familiar with Temporal, is there a way clients could have had internal defense in depth that guards against tenant leakage at the provider (Temporal) level?

jiggunjer5 mesi fa

Don't use namespaces. Wire up multi-tenant at the RBAC level. Need stronger isolation? Run another cluster.

UltraSane5 mesi fa

Encrypting tenant data with per tenant keys is a good defense against this kind of thing.

bdj1085 mesi fa

Things like this are inevitable, especially these days.