| パッケージ | 影響を受けるバージョン | 修正済みバージョン |
|---|---|---|
| n8n | ≥ 2.0.0, < 2.37.7≥ 2.38.0, < 2.38.2< 1.123.76 | 2.37.72.38.21.123.76 |
| n8n | ≥ 2.0.0, < 2.37.7≥ 2.38.0, < 2.38.2< 1.123.76 | 2.37.72.38.21.123.76 |
The expression compiler's sanitizer resolved through a dynamically-scoped this, so a class field named __sanitize rebound it and reached the Function constructor. On the backend, any expression author could run code in the n8n process; in the editor preview, a member's expression could run as JavaScript in the session of whoever opened the workflow. The patch rejects reserved class-member names.
The issue has been fixed in n8n versions 1.123.76, 2.37.7, and 2.38.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_EXPRESSION_ENGINE=vm.These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
これらの製品をお使いですか？サイトをスキャンして、脆弱なバージョンが公開されていないか確認しましょう。
無料でサイトをスキャン