Paperclip: codex_local inherited ChatGPT/OpenAI-connected Gmail and was able to send real email
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
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.
Affected packages
npm paperclipai
- Affected
- <= 2026.403.0
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-gqqj-85qm-8qhf lists affected ranges: npm paperclipai >=0 <=2026.403.0
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-gqqj-85qm-8qhf lists affected ranges: npm paperclipai >=0 <=2026.403.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Summary A Paperclip-managed codexlocal 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: - mcpcodexappsgmailgetprofile - mcpcodexappsgmailsearchemails - mcpcodexappsgmailsendemail The 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: -…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-gqqj-85qm-8qhf
- Revision 1 · created ·
Published from osv record GHSA-gqqj-85qm-8qhf
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-gqqj-85qm-8qhf Advisory: Paperclip: codex_local inherited ChatGPT/OpenAI-connected Gmail and was able to send real email IDs: GHSA-gqqj-85qm-8qhf Record: https://patchnext.com/advisories/ghsa-gqqj-85qm-8qhf (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.7) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - npm paperclipai: affected <= 2026.403.0 ## Suggested inspection (read-only) - `npm ls paperclipai --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on paperclipai. - 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-gqqj-85qm-8qhf (OSV record GHSA-gqqj-85qm-8qhf lists affected ranges: npm paperclipai >=0 <=2026.403.0) - Verified: https://github.com/advisories/GHSA-gqqj-85qm-8qhf (GitHub-reviewed advisory GHSA-gqqj-85qm-8qhf lists affected ranges: npm paperclipai >=0 <=2026.403.0) Commands are suggestions: review each one before running it.
Loading voting…