Paperclip Authorization Flaw Could Enable Server-Side Code Execution

Summary
CVE-2026-41679, a critical Paperclip authorization bypass, could let attackers on network-accessible instances with default authenticated-mode settings reach code execution as the server process. Paperclip fixed the flaw and two other bugs.
Key points
- Oasis Security reported CVE-2026-41679, rated CVSS 10, in Paperclip.
- On affected network-accessible instances, an attacker could self-register without email verification and use the CLI authorization flow to obtain a board API token.
- The company import path required board-level access rather than instance-admin privileges, allowing an attacker to import a company with a crafted .paperclip.yaml.
- The imported agent could use a host-level execution adapter to run commands with the Paperclip server process’s permissions.
- Paperclip fixed the issue by adding authorization checks to import preview and execution flows and tightening company scoping.
- Oasis also reported an API authorization bug that could expose sensitive data and a loopback DNS rebinding weakness that could enable code execution on developer machines.
Article Details
- Vulnerability Types
- Authorization bypass
- DNS rebinding
- Severity
- Critical (CVSS 10)
- Exploitation Status
- unknown
- Exploit Availability
- unknown
- Patch Status
- available
MITRE ATT&CK
T1059 · Command and Scripting InterpreterA crafted company import could configure an agent command for execution by the Paperclip server process; DNS rebinding could also lead to command execution on a developer's computer.T1189 · Drive-by CompromiseA developer loading an attacker-controlled website could have its JavaScript use DNS rebinding to access the local Paperclip API.T1190 · Exploit Public-Facing ApplicationA network attacker could exploit authorization flaws in network-accessible Paperclip instances to access company import routes.
