Cross-User Agent Chat Resume Allows Hijacking Another User's Pending Tool Approval
GHSA-p3pg-xw4f-m72c · published 2026-09-30
- Severity
- Medium
- CVSS score
- 6.1
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 2.42.0
The endpoint that resumes a suspended agent tool call accepted a run identifier from the request body without checking that the checkpoint belonged to the caller. Two sibling read endpoints were scoped to the project rather than to the user, so any member of that project could list another member's private agent conversations, read them in full, and then answer a pending approval on their behalf. The tool ran and its result was written into the victim's own conversation.
Upgrade n8n to 2.42.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
The issue has been fixed in n8n versions 2.42.0 and 2.41.4. Users should upgrade to one of these versions or later to remediate the vulnerability.
If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Restrict n8n instance access to fully trusted users only. Disable the Agents module if it is not required by removing it from N8N_ENABLED_MODULES. Limit team project membership to the minimum set of users who require access to shared agents. Avoid using tools with "Require approval" enabled on agents accessible to multiple project members until the instance is patched. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalFlowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromiumflowise, flowise-components
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- Criticaln8n Has an Arbitrary File Read via Git Noden8n, n8n, n8n
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- Criticaln8n has XML Node Prototype Pollution that to RCEn8n, n8n, n8n
- Criticaln8n has Prototype Pollution in XML Webhook Body Parser that Leads to RCEn8n, n8n, n8n
The impact, patch and workaround text comes from the advisory, shortened (published by n8n). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.