# CVE-2026-103248: n8n before 1.123.80, 2.39.6, and 2.40.1 PostgREST Filter Injection via Supabase

> Attackers can inject PostgREST filters via untrusted input in n8n's Supabase node to read, update, or delete database records.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-c6j4-7wv3-xqf9, GHSA-xrqg-3xcp-h45x, MINI-v529-456v-p76r

## What is CVE-2026-103248?

CVE-2026-103248 is a high-severity SQL injection vulnerability in n8n-io n8n, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain a filter injection vulnerability in the Supabase node's Filters (String) mode that fails to escape field values. Attackers can inject filter expressions from untrusted input to read all table rows, update all records, or delete entire tables in a single request.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-103248?


## How do I fix CVE-2026-103248?

Upgrade to a fixed version.

## Is CVE-2026-103248 being exploited?

There is no known exploitation of CVE-2026-103248 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103248 and fix it if it is affected.

What it is: CVE-2026-103248 is a high-severity SQL injection vulnerability in n8n-io n8n, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-103248 in the wild and no public exploit code.

Affected product: n8n-io n8n. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-103248/ (Markdown: https://insights.sbomify.com/CVE-2026-103248/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103248
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103248
- OSV: https://osv.dev/vulnerability/CVE-2026-103248

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-103248/
Summaries are generated and may contain mistakes; the official description above is the record.