Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Low severity, with a CVSS score of 3.1, published 16 April 2026.
- Which products and versions are affected?
- @paperclipai/server (npm) SEMVER:introduced=0,fixed=2026.416.0.
- Is there a fix for This vulnerability?
- Yes. @paperclipai/server (npm): upgrade to 2026.416.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network.
- Am I affected?
- Check whether you run @paperclipai/server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @paperclipai/server (npm): upgrade to 2026.416.0 or later
npm install @paperclipai/server@2026.416.0
Technical details
The vulnerability is a missing authentication check (CWE-306) affecting multiple API endpoints across authenticated deployments. Four classes of issues exist: (1) GET /api/heartbeat-runs/:runId/issues lacks assertCompanyAccess, exposing issue data; (2) POST /api/cli-auth/challenges has no actor verification, returning pre-generated boardApiTokens; (3) GET /api/skills/* endpoints leak complete agent instructions, API maps, and authentication protocols; (4) GET /api/health exposes deployment mode, version, and feature flags. The root cause is reliance on per-endpoint authentication checks rather than middleware-level enforcement; unauthenticated requests receive actor: {type: "none"} and pass through to route handlers that may skip verification. Attack requires only network access; no authentication or user interaction needed. Fix was released in version 2026.416.0.
Affected products
- Paperclip AI Server prior to 2026.416.0
Timeline
- 2026-04-16: disclosed
- 2026-04-16: patched: Fixed in version 2026.416.0