What happened
Downstream agents invoked file-reading tools and disclosed protected experiment secrets in E11; executors created unauthorized marker files in E12.
2026-11-16
MediumPrimaryControlled orchestration tests found forged reviewer approvals caused marker-file creation and unchecked delegation disclosed experiment-specific secrets.
What happened
Downstream agents invoked file-reading tools and disclosed protected experiment secrets in E11; executors created unauthorized marker files in E12.
Why it matters
No production compromise is reported. Observed effects were experiment-specific secret disclosure and marker files in controlled VM/workspace configurations.
Missing authorization check
Authenticated reviewer approval bound to the requested write, and verification of originating-principal authority before delegated secret access.
Would PP block it?
Complete mediation could hold a file read or write when the originating principal lacks authority. The paper evaluates its own protected implementations, not PP, and establishes no PP efficacy.
Incident analysis
2026-11-16
Authors publish the preprint reporting controlled delegation and identity-spoofing outcomes.
Authorization boundary
This incident is categorized as Governance bypass. The relevant Permission Protocol gate is Tool-Call Gate. The read is conditional: the block only applies where the real action boundary is routed through a gate.
An independently integrated tool boundary could require verified, action-bound authority instead of trusting textual approvals or inherited tool privileges.
Related incidents and controls
Start small
This incident maps to Tool-Call Gate. Start with the boundary that controls the actual action, then require a signed receipt before execution.