Quick answers
- Is CVE-2026-119713 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119713 being exploited in the wild.
- How severe is CVE-2026-119713?
- High severity, with a CVSS score of 8.8, published 30 October 2026.
- Which products and versions are affected?
- Paperclip AI Paperclip 2026.403.0 before 2026.416.0.
- Is there a fix for CVE-2026-119713?
- Yes: fixed in 2026.416.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119713 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-119713?
- Check whether you run Paperclip AI Paperclip at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2026.416.0
Technical details
The vulnerability is a command injection flaw in the execution-workspaces API endpoint. An authenticated attacker with a valid API key can modify the cleanupCommand and teardownCommand fields via PATCH /api/execution-workspaces/:id; these commands are later executed unsanitized through a shell by the cleanupExecutionWorkspaceArtifacts process when the workspace is archived, allowing arbitrary code execution in the security context of the Paperclip server.
Affected products
- Paperclip AI Paperclip 2026.403.0 before 2026.416.0
Timeline
- 2026-10-30: disclosed: Vulnerability published