<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 15:27:08 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-292783</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-292783</link>
      <description>EUVD-2026-292783</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-292783</guid>
    </item>
    <item>
      <title>fkie_cve-2026-41679</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-41679</link>
      <description>&lt;p&gt;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&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-41679</guid>
    </item>
    <item>
      <title>GHSA-68qg-g8mg-6pr7 — paperclip Vulnerable to Unauthenticated Remote Code Execution via Import Authorization Bypass</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-68qg-g8mg-6pr7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: paperclipai, npm: @paperclipai/server&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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&amp;#39;s address. The entire chain is six API calls.&lt;/p&gt;
&lt;p&gt;I verified every step against the latest version. I have a fully automated PoC script and a video recording available.&lt;/p&gt;
&lt;p&gt;Discord: sagi03581&lt;/p&gt;
&lt;p&gt;## Steps to Reproduce&lt;/p&gt;
&lt;p&gt;The attack chains four independent flaws to escalate from zero access to RCE:&lt;/p&gt;
&lt;p&gt;### Step 1: Create an account (no invite, no email verification)&lt;/p&gt;
&lt;p&gt;```bash
curl -s -X POST -H &amp;#34;Content-Type: application/json&amp;#34; \
  -d &amp;#39;{&amp;#34;email&amp;#34;:&amp;#34;attacker@evil.com&amp;#34;,&amp;#34;password&amp;#34;:&amp;#34;P@ssw0rd123&amp;#34;,&amp;#34;name&amp;#34;:&amp;#34;attacker&amp;#34;}&amp;#39; \
  http://&amp;lt;target&amp;gt;:3100/api/auth/sign-up/email
```&lt;/p&gt;
&lt;p&gt;Returns a valid account immediately. No invite token required, no email verification.&lt;/p&gt;
&lt;p&gt;This works because `PAPERCLIP_AUTH_DISABLE_SIGN_UP` defaults to `false` in `server/src/config.ts:169-173`:&lt;/p&gt;
&lt;p&gt;```typescript
const authDisableSignUp: boolean =
  disableSignUpFromEnv !== undefined
    ? disableSignUpFromEnv === &amp;#34;true&amp;#34;
    : (fileConfig?.auth?.disableSignUp ?? false);   // default: open
```&lt;/p&gt;
&lt;p&gt;And email verification is hardcoded off in `server/src/auth/better-auth.ts:89-93`:&lt;/p&gt;
&lt;p&gt;```typescript
emailAndPassword: {
  enabled: true,
  requireEmailVerification: false,
  disableSignUp: config.authDisableSignUp,
},
```&lt;/p&gt;
&lt;p&gt;The environment variable isn&amp;#39;t documented in the deployment guide, so operators don&amp;#39;t know it exis…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: paperclipai, npm: @paperclipai/server&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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&amp;#39;s address. The entire chain is six API calls.&lt;/p&gt;
&lt;p&gt;I verified every step against the latest version. I have a fully automated PoC script and a video recording available.&lt;/p&gt;
&lt;p&gt;Discord: sagi03581&lt;/p&gt;
&lt;p&gt;## Steps to Reproduce&lt;/p&gt;
&lt;p&gt;The attack chains four independent flaws to escalate from zero access to RCE:&lt;/p&gt;
&lt;p&gt;### Step 1: Create an account (no invite, no email verification)&lt;/p&gt;
&lt;p&gt;```bash
curl -s -X POST -H &amp;#34;Content-Type: application/json&amp;#34; \
  -d &amp;#39;{&amp;#34;email&amp;#34;:&amp;#34;attacker@evil.com&amp;#34;,&amp;#34;password&amp;#34;:&amp;#34;P@ssw0rd123&amp;#34;,&amp;#34;name&amp;#34;:&amp;#34;attacker&amp;#34;}&amp;#39; \
  http://&amp;lt;target&amp;gt;:3100/api/auth/sign-up/email
```&lt;/p&gt;
&lt;p&gt;Returns a valid account immediately. No invite token required, no email verification.&lt;/p&gt;
&lt;p&gt;This works because `PAPERCLIP_AUTH_DISABLE_SIGN_UP` defaults to `false` in `server/src/config.ts:169-173`:&lt;/p&gt;
&lt;p&gt;```typescript
const authDisableSignUp: boolean =
  disableSignUpFromEnv !== undefined
    ? disableSignUpFromEnv === &amp;#34;true&amp;#34;
    : (fileConfig?.auth?.disableSignUp ?? false);   // default: open
```&lt;/p&gt;
&lt;p&gt;And email verification is hardcoded off in `server/src/auth/better-auth.ts:89-93`:&lt;/p&gt;
&lt;p&gt;```typescript
emailAndPassword: {
  enabled: true,
  requireEmailVerification: false,
  disableSignUp: config.authDisableSignUp,
},
```&lt;/p&gt;
&lt;p&gt;The environment variable isn&amp;#39;t documented in the deployment guide, so operators don&amp;#39;t know it exis…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-68qg-g8mg-6pr7</guid>
    </item>
  </channel>
</rss>
