paperclipai
Affected
- introduced
0, last affected2026.403.0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Paperclip: codex_local inherited ChatGPT/OpenAI-connected Gmail and was able to send real email
Summary
A Paperclip-managed codex_local runtime was able to access and use a Gmail connector that I had connected in the ChatGPT/OpenAI apps UI, even though I had not explicitly connected Gmail inside Paperclip or separately inside Codex.
In my environment this enabled mailbox access and a real outbound email to be sent from my Gmail account. After I manually intervened to stop the workflow, follow-up retraction messages were also sent, confirming repeated outward write/send capability.
This appears to be a trust-boundary failure between Paperclip-managed Codex execution and inherited OpenAI app connectors, amplified by dangerous-by-default runtime settings.
Details
Successful runtime calls include:
mcp__codex_apps__gmail_get_profilemcp__codex_apps__gmail_search_emailsmcp__codex_apps__gmail_send_emailThe connected Gmail profile resolved to my personal account.
Inside the Paperclip-managed codex-home, I also found cached OpenAI curated connector state for Gmail under a path like:
codex-home/plugins/cache/openai-curated/gmail/.../.app.jsonThis strongly suggests that the runtime had access to an already connected OpenAI apps surface rather than a Paperclip-specific Gmail integration that I intentionally configured.
Separately, in the installed Paperclip code, codex_local defaults dangerouslyBypassApprovalsAndSandbox to true, and the server-side agent creation path applies that default when the flag is omitted. In practice, that makes this boundary failure much more dangerous because a newly created codex_local agent can operate with approvals and sandbox bypassed by default.
The key issue is this: I had connected Gmail only in the ChatGPT/OpenAI apps UI. I had not intentionally connected Gmail inside Paperclip or separately inside Codex. Despite that, the Paperclip-managed codex_local runtime was able to use Gmail read/write actions.
PoC
Environment:
codex_localcodex_local agent created and run with default behaviorObserved reproduction path:
codex_local agent.mcp__codex_apps__gmail_get_profilemcp__codex_apps__gmail_search_emailsmcp__codex_apps__gmail_send_emailPrivate evidence available on request:
get_profile / search / send logscodex-home Gmail connector cache path(s)send_email, send_draft, and update_draft exposed in the connected-app UIImpact
This was not only theoretical in my environment. It resulted in:
From an operator/security perspective, connecting Gmail in the ChatGPT/OpenAI apps UI should not automatically make that connector available to a Paperclip-managed local agent runtime, especially not for write/send actions.
One or more of the following:
codex_local runsdangerouslyBypassApprovalsAndSandbox = falseHigh Basis: The source's own band: HIGH
0, last affected 2026.403.0 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0