# CVE-2026-103258: n8n before 2.39.6 and 2.40.x before 2.40.1 Filter Bypass via Parameter Interpolation

> Attackers can bypass filters in n8n nodes to expose bulk data like contact lists and tickets by exploiting unescaped parameter interpolation.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **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:** 6 Oct 2026
- **Also known as:** GHSA-5pg9-2vqx-r6jm, GHSA-fr2j-m9j7-53r7, MINI-crh7-v6wv-8vq7

## What is CVE-2026-103258?

CVE-2026-103258 is a medium-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 2.39.6 and 2.40.0 before 2.40.1 contain an unescaped parameter interpolation vulnerability in SendGrid, Freshservice, and ServiceNow nodes that allows attackers to bypass filters by breaking out of query literals. Attackers can exploit this by binding vulnerable node parameters to untrusted external input to widen single-record lookups into match-all queries, exposing bulk data including contact lists, tickets, and directory entries.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)

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


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

Upgrade to a fixed version.

## Is CVE-2026-103258 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103258 is a medium-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-103258 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-103258/ (Markdown: https://insights.sbomify.com/CVE-2026-103258/index.md)
```

## Sources

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

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