| パッケージ | 影響を受けるバージョン | 修正済みバージョン |
|---|---|---|
| n8n | ≥ 2.0.0, < 2.25.7≥ 2.26.0, < 2.26.2< 1.123.55 | 2.25.72.26.21.123.55 |
| n8n | ≥ 2.0.0-rc.0, < 2.25.7≥ 2.26.0, < 2.26.2< 1.123.55 | 2.25.72.26.21.123.55 |
An authenticated user with workflow edit access could configure a Respond to Webhook node to serve binary content with an attacker-controlled Content-Type. The binary response path bypassed the central Content-Security-Policy sandbox header, allowing a public webhook to execute JavaScript in the n8n origin when visited by an authenticated user, with access to that user's session.
The issue has been fixed in n8n versions 1.123.55, 2.25.7, and 2.26.2. 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:
n8n-nodes-base.respondToWebhook to the NODES_EXCLUDE environment variable.These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
これらの製品をお使いですか？サイトをスキャンして、脆弱なバージョンが公開されていないか確認しましょう。
無料でサイトをスキャン