Paperclip: Unauthenticated Access to Multiple API Endpoints in Authenticated Mode

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary Several API endpoints in authenticated mode have no authentication at all. They respond to completely unauthenticated requests with sensitive data or allow state-changing operations. No account, no session, no API key needed. Verified against the latest version. Discord: sagi03581 Steps to Reproduce 1. Unauthenticated issue data access GET /api/heartbeat-runs/:runId/issues returns issue data for a heartbeat run with zero authentication. Every other endpoint in server/src/routes/activity.ts calls assertCompanyAccess, but this one was missed. If an attacker obtains a valid run UUID (from logs, error messages, shared URLs, or by probing), they can read issue data without any credentials. 2. Unauthenticated CLI auth challenge creation POST /api/cli-auth/challenges creates a CLI authentication challenge with no actor check at all. The handler at server/src/routes/access.ts:1638-1659 skips any auth verification. The response includes a boardApiToken that becomes active once the…

Published by the source

16 Apr 2026, 22:47 UTC

Last modified by the source

16 Apr 2026, 23:06 UTC

Source last checked

26 Oct 2026, 12:48 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-xfqj-r5qw-8g4j

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-xfqj-r5qw-8g4j

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

# Patch Next advisory brief: GHSA-xfqj-r5qw-8g4j

Advisory: Paperclip: Unauthenticated Access to Multiple API Endpoints in Authenticated Mode
IDs: GHSA-xfqj-r5qw-8g4j
Record: https://patchnext.com/advisories/ghsa-xfqj-r5qw-8g4j (revision 2, 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: High (CVSS 8.3)
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://osv.dev/vulnerability/GHSA-xfqj-r5qw-8g4j (OSV record GHSA-xfqj-r5qw-8g4j lists affected ranges: npm @paperclipai/server >=0 <2026.416.0 (fixed))
- Verified: https://github.com/advisories/GHSA-xfqj-r5qw-8g4j (GitHub-reviewed advisory GHSA-xfqj-r5qw-8g4j lists affected ranges: npm @paperclipai/server >=0 <2026.416.0)

Commands are suggestions: review each one before running it.