AIKIDO-2026-21865

TL;DR

The HashiCorp Vault secrets backend's team scoped lookup uses a team agnostic {base_path}/{key} path built from the caller supplied variable or connection key when that lookup finds no value. In a multi team deployment, a Dag author scoped to one team can supply a key that matches this shared fallback path and read a secret that belongs to a different team. The Execution API Variables route accepts this path shaped key directly from ordinary Dag code, so no elevated access is required to reach it. The fix removes the team agnostic fallback and uses an explicit, ordered list of configured base paths.