Skip to content
PERMISSION/PROTOCOL
Back to incident tracker

2026-11-16

MediumPrimary

Forged Reviewer Approvals and Unchecked Delegation Caused Agent File Creation and Secret Disclosure in Controlled Tests

Controlled orchestration tests found forged reviewer approvals caused marker-file creation and unchecked delegation disclosed experiment-specific secrets.

LangChain, LangGraph, AutoGen and OpenClawGovernance bypassControlled inter-agent delegation and reviewer identity-spoofing demonstrationResearch Ubuntu VM and experiment-specific workspaces; not a production deployment.

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

Timeline and technical read

Timeline

  1. 2026-11-16

    Authors publish the preprint reporting controlled delegation and identity-spoofing outcomes.

Technical breakdown

  • E11 embeds a claimed administrative delegation in a project summary and forwards it to a privileged downstream agent.
  • Without origin-authority checks, the downstream agent reads and discloses the experiment secret across the four tested configurations.
  • E12 supplies a fabricated reviewer identity and approval; vulnerable executors invoke tools and create markers.
  • Protected E11/E12 configurations reject unauthorized requests before privileged execution. Their implementation-specific checks are not uniform native framework guarantees.

Authorization boundary

Where the authorization boundary should have been

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.

If enforced at
Integrated delegation authorization and file-read/file-write execution boundaries.
Still needs
PP does not establish reviewer identity by itself, repair framework configurations, resolve all filesystem races or constrain bypass paths. Trusted principal binding and complete mediation remain necessary.
Receipt required for
Delegated protected-file access and marker creation bound to verified principal, action and exact target.

An independently integrated tool boundary could require verified, action-bound authority instead of trusting textual approvals or inherited tool privileges.

Start small

Put the relevant gate at this action boundary.

This incident maps to Tool-Call Gate. Start with the boundary that controls the actual action, then require a signed receipt before execution.

Replay this incident with a signer in the loop