Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-265w-rf2w-cjh4
No affected components available
Summary
Paperclip contains a privilege escalation vulnerability that allows an attacker with an Agent API key to execute arbitrary OS commands on the Paperclip server host. An attacker with an agent credential can escalate privileges from the agent runtime to the Paperclip server host. The vulnerability occurs because agents are allowed to update their own adapterConfig via the /agents/:id API endpoint. The configuration field adapterConfig.workspaceStrategy.provisionCommand is later executed by the server runtime using:
spawn("/bin/sh", ["-c", command])
As a result, an attacker controlling an agent credential can inject arbitrary shell commands which are executed by the Paperclip server during workspace provisioning. This breaks the intended trust boundary between agent runtime configuration and server host execution, allowing a compromised or malicious agent to escalate privileges and run commands on the host system. This vulnerability allows remote code execution on the server host.
Details
Rootcause
Agent configuration can be modified through the API endpoint:
PATCH /api/agents/:id
The validation schema allows arbitrary configuration fields:
adapterConfig: z.record(z.unknown())
This allows attackers to inject arbitrary keys into the adapter configuration object. Later, during workspace provisioning, the server runtime executes a shell command derived directly from this configuration. Relevant code path:
server/src/services/workspace-runtime.ts
adapterConfig.workspaceStrategy.provisionCommand
↓
provisionExecutionWorktree()
↓
runWorkspaceCommand(...)
↓
spawn("/bin/sh", ["-c", input.command])
Example logic:
const provisionCommand = asString(input.strategy.provisionCommand, "").trim()
await runWorkspaceCommand({
command: provisionCommand
})
Inside runWorkspaceCommand the command is executed using:
spawn(shell, ["-c", input.command])
Because no validation, escaping, or allowlist is applied, attacker-controlled configuration becomes a direct OS command execution primitive.
Affected Files
server/src/services/workspace-runtime.ts
Functions involved:
realizeExecutionWorkspace()
provisionExecutionWorktree()
runWorkspaceCommand()
Attacker Model
Required privileges: Attacker needs:
Agent API key
This credential is intended for agent automation and should not grant host-level execution privileges. Agent credentials may also be exposed to external runtimes, plugins, or third-party agent providers. Allowing such credentials to configure host-executed commands creates a privilege escalation vector. No board or administrator access is required.
Attacker Chain
Complete exploit chain:
Attacker obtains Agent API key
↓
PATCH /api/agents/:id
↓
Inject adapterConfig.workspaceStrategy.provisionCommand
↓
POST /api/agents/:id/wakeup
↓
Server executes workspace provisioning
↓
workspace-runtime.ts
↓
spawn("/bin/sh -c")
↓
Arbitrary command execution on server host
Trust Boundary Violation
Paperclip’s architecture assumes the following separation:
Agent runtime
↓
Paperclip control plane
↓
Server host OS
Agents should only perform workflow automation tasks through the orchestration layer.
However, because agent-controlled configuration is executed directly by the server runtime, the boundary collapses:
Agent configuration
↓
Server command execution
This allows an agent to execute commands outside its intended permissions.
Why This Is a Vulnerability (Not Expected Behavior)
The provisionCommand field appears intended for trusted operators configuring workspace strategies. However, the current API design allows agents themselves to modify this configuration. Because agent credentials are designed for automation and may be exposed to agent runtimes, plugins, or external providers, allowing them to configure commands executed by the host introduces a privilege escalation vector. Therefore:
Operator-controlled configuration → expected feature
Agent-controlled configuration → privilege escalation vulnerability
The vulnerability arises from insufficient separation between configuration authority and execution authority.
PoC
The following PoC demonstrates safe command execution by writing a marker file on the server. The PoC does not modify system state beyond creating a file.
Step 1 — Setup Environment
Run Server:
$env:SHELL = "C:\Program Files\Git\bin\sh.exe"
npx paperclipai onboard --yes
Login Claude:
claude
/login
Step 2 — Obtain Agent API key
Create an agent via the UI or CLI and obtain its API key. Example:
pcp_xxxxxxxxxxxxxxxxxxxxx
Step 3 — Identify agent ID
GET /api/agents/me
Step 4 — Inject malicious configuration
PATCH /api/agents/{agentId}
Step 5 — Trigger execution
POST /api/agents/{agentId}/wakeup
Step 6 — Verify command execution
<img width="1231" height="347" alt="image" src="https://github.com/user-attachments/assets/559c483b-077e-42dd-9309-6a5e5c6a3bdc" /> The marker file appears on the server filesystem: ``` ~/.paperclip/worktrees/.../poc_rce.txt ``` Example content: ``` PAPERCLIP_RCE ``` This confirms that attacker-controlled commands executed on the server.Impact
Successful exploitation allows:
Remote command execution on the Paperclip server
Potential attacker actions:
read environment variables
exfiltrate secrets
modify repositories
access database credentials
execute reverse shells
persist on host
Because Paperclip orchestrates multiple agents and repositories, this can lead to full compromise of the deployment environment. This effectively allows a malicious agent to escape the orchestration layer and execute arbitrary commands on the server host.
Recommended Fix
- Restrict configuration authority Agents should not be able to modify execution-sensitive configuration fields. Example mitigation:
deny adapterConfig.workspaceStrategy modification from agent credentials
- Server-side allowlist Only allow trusted configuration keys. Example:
adapterConfig.workspaceStrategy.provisionCommand
should only be configurable by board/admin actors.
- Avoid shell execution Instead of:
spawn("/bin/sh", ["-c", command])
prefer:
spawn(binary, args)
or a restricted command runner.
- Input validation Reject commands containing shell operators:
|
&
;
$
`
- Sandboxed workspace execution Workspace provisioning should run in a restricted environment (container / sandbox).
Minimal Patch Suggestion
One possible mitigation is to prevent agent principals from modifying execution-sensitive configuration fields such as workspaceStrategy.provisionCommand.
For example, during agent configuration updates, the server can explicitly reject this field when the request is authenticated using an Agent API key.
Example TypeScript guard:
// reject agent-controlled provisionCommand
if (
request.auth?.principal === "agent" &&
body?.adapterConfig?.workspaceStrategy?.provisionCommand
) {
throw new Error(
"Agents are not permitted to configure workspaceStrategy.provisionCommand"
);
}
Additionally, the server should avoid executing arbitrary shell commands derived from configuration values. Instead of executing:
spawn("/bin/sh", ["-c", command])
prefer structured execution:
spawn(binary, args)
or restrict the command to a predefined allowlist.
Security Impact Statement
An authenticated attacker with an Agent API key can modify their agent configuration to inject arbitrary shell commands into workspaceStrategy.provisionCommand. These commands are executed by the Paperclip server during workspace provisioning via spawn("/bin/sh", ["-c", command]), resulting in arbitrary command execution on the host system.
Disclosure
This vulnerability was discovered during security research on the Paperclip orchestration runtime. The issue is reported privately to allow maintainers to patch before public disclosure.
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information. There is a high impact on the integrity of the data. There is a high impact on the availability of the system.
Exploitation activity has been observed. Apply available patches or mitigations urgently.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard