paperclip: Improper Authentication
CVE-2026-41679 is a critical-severity improper authentication vulnerability in paperclip from Paperclipai, with a CVSS 3.1 base score of 10.0 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected paperclip versions: < 2026.410.0. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 31.7% chance of exploitation within 30 days, which is in the top 1.68% of all scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Paperclipai to 2026.416.0 or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Paperclipai | paperclip | < 2026.410.0 | Not stated |
| Paperclipai | @paperclipai/server | < 2026.410.0 | Not stated |
| Paperclip | Paperclipai | before 2026.416.0 | 2026.416.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (github.com).
Official description
Paperclip is a Node.js server and React UI that orchestrates a team of AI agents to run a business. Prior to version 2026.416.0, an unauthenticated attacker can achieve full remote code execution on any network-accessible Paperclip instance running in `authenticated` mode with default configuration. No user interaction, no credentials, just the target's address. The chain consists of six API calls. The attack is fully automated, requires no user interaction, and works against the default deployment configuration. Version 2026.416.0 patches the issue.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Authentication
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
How developers prevent this class of flaw
- Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/paperclipai/paperclip/security/advisories/GHSA-68qg-g8mg-6pr7Exploit, Mitigation, Third Party Advisory
Other vulnerabilities in paperclip
- 9.6 Critical severity
Recent Improper Authentication vulnerabilities
- 9.8 Critical severity
- 8.2 High severity
- 8.2 High severity
- 9.2 Critical severity
- 9.1 Critical severity
- 7.6 High severity
Spotted an error? Tell us.