# CVE-2026-119713: Paperclip 2026.403.0 before 2026.416.0 RCE via Execution Workspace Cleanup Commands


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 30 Oct 2026
- **Also known as:** GHSA-832j-x75x-r6jc, GHSA-vr7g-88fq-vhq3

## What is CVE-2026-119713?

CVE-2026-119713 is a high-severity vulnerability in @paperclipai/server, published on 30 Oct 2026. 

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-119713?

1 open source package ship an affected version, including @paperclipai/server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@paperclipai/server` | npm | All versions | 2026.416.0 |

## How do I fix CVE-2026-119713?

Upgrade @paperclipai/server to 2026.416.0 or later.

## Is CVE-2026-119713 being exploited?

There is no known exploitation of CVE-2026-119713 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119713 and fix it if it is affected.

What it is: CVE-2026-119713 is a high-severity vulnerability in @paperclipai/server, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119713 in the wild and no public exploit code.

Affected packages and fixed versions:
- @paperclipai/server (npm): affected all versions; fixed in 2026.416.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119713/ (Markdown: https://insights.sbomify.com/CVE-2026-119713/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119713
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119713
- OSV: https://osv.dev/vulnerability/CVE-2026-119713

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119713/
Summaries are generated and may contain mistakes; the official description above is the record.