In deployments using multi-team mode with a team-aware auth manager, the asset materialization endpoint `POST /api/v2/assets/{asset id}/materialize` and the XCom result check on `wait dag run until finished` authorize the target Dag without verifying its team. This occurs because the auth manager checks the `DAG` resource instead of the `DAG:<team>` resource, bypassing team-scoped permissions. Consequently, an authenticated user from one team can trigger Dag runs belonging to another team by providing their own `dag run id` and `conf`, and can read XCom values from another team. Deployments using the FAB auth manager are not affected.