n8n before 1.123.69 PostgREST Filter Injection via Supabase
n8n-io n8n
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
n8n-io n8n
| Product | Affected | Fixed in |
|---|---|---|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
n8n before 1.123.69, 2.33.4, and 2.34.1 contains a PostgREST filter injection vulnerability in the Supabase node's Row Get Many, Delete, and Update operations, which built filter queries by concatenating an expression-bindable value without escaping. An attacker could inject a condition that widened the filter to match every row, turning an intended single-row operation into full-table disclosure, deletion, or modification.
From the CVE record · VulnCheck
The Supabase node’s Row Get Many, Delete, and Update operations build PostgREST filters without escaping an expression-bindable value. If an attacker can control that value, they can widen a filter to match every row, potentially disclosing, deleting, or modifying an entire table. The input does not specify authentication or user-interaction requirements.
Engineers running n8n versions before 1.123.69, 2.33.4, or 2.34.1 should check their installations.