CVE-2026-41679

paperclip Vulnerable to Unauthenticated Remote Code Execution via Import Authorization Bypass

An unauthenticated remote attacker can execute arbitrary commands as the Paperclip server's OS user on any authenticated mode deployment with default configuration. This gives them:

• Full filesystem access (read/write as the server user)
• Access to all data in the Paperclip database
• Ability to pivot to internal network services
• Ability to disrupt all agent operations

The attack is fully automated, requires no user interaction, and works against the default deployment configuration.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2026-41679 has a CVSS score of 10.0 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.410.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-41679? CVE-2026-41679 is a critical-severity improper authentication vulnerability in paperclipai (npm), affecting versions < 2026.410.0. It is fixed in 2026.410.0. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2026-41679? CVE-2026-41679 has a CVSS score of 10.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-41679?
   • paperclipai (npm) (versions < 2026.410.0)
   • @paperclipai/server (npm) (versions < 2026.410.0)
4. Is there a fix for CVE-2026-41679? Yes. CVE-2026-41679 is fixed in 2026.410.0. Upgrade to this version or later.
5. Is CVE-2026-41679 exploitable, and should I be worried? Whether CVE-2026-41679 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-41679 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-41679?
   • Upgrade paperclipai to 2026.410.0 or later
   • Upgrade @paperclipai/server to 2026.410.0 or later