AIKIDO-2026-869451

TL;DR

The Azure Key Vault secrets backend supports team-scoped secret lookups for multi-team deployments, probing a team-scoped name before falling back to a team-agnostic name. A guard meant to reject identifiers that spell another team's namespace never runs when a team scope is supplied, so a team-scoped lookup that misses falls through and resolves the named secret. A caller authorized for one team can supply a secret identifier that spells out another team's namespace and read that team's secret value. The fix refuses the team-agnostic fall-through for any identifier that spells a team-scoped name, applies the same ambiguous-identifier refusal to the configuration lookup, and gates the behavior on multi-team mode.