What happened
The researcher directs the agent to write and select a workspace shell; Nanobot launches that shell outside bwrap, and it copies a protected canary under the non-root nanobot account.
2026-11-17
HighPrimaryTenable reports a controlled Nanobot agent shell-override bypass that copied an out-of-workspace canary before bwrap containment. Fixed in version 0.4.1.
What happened
The researcher directs the agent to write and select a workspace shell; Nanobot launches that shell outside bwrap, and it copies a protected canary under the non-root nanobot account.
Why it matters
A controlled out-of-workspace host-file copy was reported. The advisory describes access to host resources available to the service account; it does not establish a malicious campaign, root access or customer-secret theft.
Missing authorization check
Independent validation of the effective interpreter identity, executable provenance and filesystem scope before launching any agent-selected process.
Would PP block it?
A gate mediating the actual host executable could bind approved interpreter identity, arguments and filesystem scope to delegated authority. Basename-only approval is insufficient. This advisory does not test Permission Protocol or establish a prevention result.
Incident analysis
2026-09-28
Tenable reports the issue through GitHub.
2026-11-04
Tenable confirms additional fixes; the vendor reports the fix merged into main pending release.
2026-11-06
The disclosure timeline records release of the fix in Nanobot 0.4.1.
2026-11-17
Tenable publishes TRA-2026-68.
Authorization boundary
This incident is categorized as Tool execution / MCP. The relevant Permission Protocol gate is Runtime Gate. The read is conditional: the block only applies where the real action boundary is routed through a gate.
An externally integrated execution boundary could reject an unapproved workspace interpreter, but a gate inside the escaped harness would not provide complete containment.
Related incidents and controls
Start small
This incident maps to Runtime Gate. Start with the boundary that controls the actual action, then require a signed receipt before execution.