01 / Attack path
How the boundary is crossed
An agent obtains approval for deployment to staging, then a mutable environment alias points to production when the executor runs.
- 01Lower-trust input
- 02Attempted instruction
- 03Protected action
- 04Enforced decision
02 / Containment
Where bounded authority limits the effect
Resolve immutable target identity and normalized parameters at execution, bind them to the decision and reject drift.
03 / Failure and evidence
The attacker’s opportunity and the defender’s record
The decision is correct for the checked object but execution affects a different object.
Retain checked resource ID, executed resource ID, binding result and observed deployment target.
04 / Canonical scope
Why this reference stands alone
Stale authorization concerns old state; this page owns a changed object or argument after a valid check.
Protocol or attack trace
Target-switch race
Policy approves deploy to alias staging, then alias points to production before commit.
Bind immutable target ID and payload digest at executor; deny alias or payload drift.
Primary references