upvote
Masked namespace vulnerability in Temporal

(depthfirst.com)

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?

reply
Things like this are inevitable, especially these days.
reply