Paperclip 2026.403.0 before 2026.416.0 RCE via Execution Workspace Cleanup Commands
Paperclip server releases from 2026.403.0 up to 2026.416.0 run execution workspace cleanup commands verbatim when a workspace is archived. Fixed in 2026.416.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 2026.416.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Paperclip 2026.403.0 before 2026.416.0 contains a remote code execution vulnerability that allows agent API key holders to set cleanupCommand and teardownCommand via PATCH /api/execution-workspaces/:id. When the workspace is archived, cleanupExecutionWorkspaceArtifacts runs these commands through a shell as the Paperclip server process, executing attacker-chosen OS commands on the server host.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- paperclipai @paperclipai/server
From 2026.403.0 · fixed in 2026.416.0
- @paperclipai/servernpm
fixed in 2026.416.0
References 6
Questions about CVE-2026-119713
What does this mean?
When an execution workspace is archived, Paperclip runs its cleanup command exactly as written. That lets arbitrary OS commands run as the Paperclip server process, which gives remote code execution on the server host.Source: github.com
Am I affected, and how do I check?
The advisory names Paperclip AI v2026.403.0, and the package data lists @paperclipai/server releases before 2026.416.0 as affected. Deployments in local_trusted or authenticated mode on Linux, macOS, or Windows with Git installed are in scope; check the installed @paperclipai/server version to see which release is running.Source: github.com
What should I do about it?
Upgrade @paperclipai/server to 2026.416.0 or later, the first release listed as fixed.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data