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?
- High severity, with a CVSS score of 8.7, published 16 April 2026.
- Which products and versions are affected?
- paperclipai (npm) <= 2026.403.0; Paperclip AI Paperclip <= 2026.403.0.
- Is there a fix for This vulnerability?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run paperclipai (npm) or Paperclip AI Paperclip 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.
Technical details
A trust-boundary failure in the Paperclip-managed 'codex_local' runtime allows it to access cached OpenAI curated connector states, such as Gmail credentials, stored in the 'codex-home' directory. This occurs even if the user has not explicitly integrated Gmail within Paperclip. The risk is further escalated by a default configuration where 'dangerouslyBypassApprovalsAndSandbox' is set to true, allowing newly created agents to perform read/write actions (like 'gmail_send_email') without user approval or sandboxing. An attacker or a misconfigured agent could leverage this to search mailboxes or send unauthorized emails using the victim's authenticated session. No patch is currently specified in the advisory.
Affected products
- Paperclip AI paperclipai/paperclip <= 2026.403.0
Timeline
- 2026-04-16: disclosed: Advisory published on GitHub