Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.9amended

Paperclip: Cross-tenant agent API token minting via missing assertCompanyAccess on /api/agents/:id/keys

GHSA-47wq-cj9q-wpmp

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@paperclipai/server 2026.416.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.9 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

<img width="7007" height="950" alt="01-setup" src="https://github.com/user-attachments/assets/1596b8d1-8de5-4c21-b1d2-2db41b568d7e" / Isolated paperclip instance running in authenticated mode (default config) on a clean Docker image matching commit b649bd4 (2026.411.0-canary.8, post the 2026.410.0 patch). This advisory was verified on an unmodified build. Summary POST /api/agents/:id/keys, GET /api/agents/:id/keys, and DELETE /api/agents/:id/keys/:keyId (server/src/routes/agents.ts lines 2050-2087) only call assertBoard to authorize the caller. They never call assertCompanyAccess and never verify that the caller is a member of the company that owns the target agent. Any authenticated board user (including a freshly signed-up account with zero company memberships and no instanceadmin role) can mint a plaintext pcp agent API token for any agent in any company on the instance. The minted token is bound to the victim agent's companyId server-side, so every downstream assertCompanyAccess…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-47wq-cj9q-wpmp

  2. Revision 2 · amended ·

    Amended from osv record GHSA-47wq-cj9q-wpmp

  3. Revision 1 · created ·

    Published from ghsa record GHSA-47wq-cj9q-wpmp

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-47wq-cj9q-wpmp

Advisory: Paperclip: Cross-tenant agent API token minting via missing assertCompanyAccess on /api/agents/:id/keys
IDs: GHSA-47wq-cj9q-wpmp
Record: https://patchnext.com/advisories/ghsa-47wq-cj9q-wpmp (revision 3, source checked 26 Oct 2026, 12:48 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @paperclipai/server 2026.416.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @paperclipai/server: affected < 2026.416.0; fixed in 2026.416.0

## Suggested inspection (read-only)
- `npm ls @paperclipai/server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @paperclipai/server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-47wq-cj9q-wpmp (GitHub-reviewed advisory GHSA-47wq-cj9q-wpmp lists affected ranges: npm @paperclipai/server >=0 <2026.416.0)
- Verified: https://osv.dev/vulnerability/GHSA-47wq-cj9q-wpmp (OSV record GHSA-47wq-cj9q-wpmp lists affected ranges: npm @paperclipai/server >=0 <2026.416.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…