A signature bypass exists in the 'waiting-webhook' endpoint. The issue occurs because the system selects Send-and-Wait validation before normalizing an alternate node reference form. An attacker possessing an execution's resume token can approve waiting executions intended for other users, allowing downstream actions to run using the workflow owner's credentials, which may lead to command execution.