Implemented
0
`N8N_POSTMESSAGE_ALLOWED_ORIGINS` empty by default → embedded editor accepts `postMessage` from any origin
Source: n8n-io/n8n#39333 · opened by @tiagovilasboas
Static review of public source at commit fe0fad574337. No traffic was sent to any n8n environment. The security config ships an empty postMessage allowlist, and the editor utils treat empty as "allow all": packages/@n8n/config/src/configs/security.config.ts: packages/frontend/editor-ui/src/app/utils/postMessageUtils.ts: (frontend.service.ts splits the env on , and filters empties, so the default '' becomes [].) Any parent page that can iframe a preview/demo embed can therefore drive editor postMessage commands until an operator sets N8N_POSTMESSAGE_ALLOWED_ORIGINS. The comment already calls this historical behavior; the remaining gap is the insecure default for new installs that enable embeds. Suggested change: • Default to same-origin only (or to APP_URL / editor origin), and treat empty as deny-by-default for new majors; or • Keep empty→allow for compatibility but emit a one-time admin warning when embeds are used with an empty allowlist; or …
No pledges yet. Be the first to back this.
Comments
Similar requests
Feature: Add configurable request-body validation to the Webhook node
0 votes · 0 comments
AI Agent: return tool-schema validation failures to the model as recoverable errors instead of terminating the execution
0 votes · 0 comments
Anthropic Chat Model: expose "strict": true for client tool definitions
0 votes · 0 comments
HTTP Request does not refresh credentials when the API reports expiry in the response body
0 votes · 0 comments
No comments yet.