CVE-2026-103258: n8n: unescaped parameter interpolation exposes bulk data
MEDIUMn8n versions before 2.39.6 (and 2.40.0 before 2.40.1) fail to escape parameters in the SendGrid, Freshservice and ServiceNow nodes, so an attacker who controls a bound input can turn a single-record lookup into a match-all query. The result is bulk disclosure of contact lists, tickets and directory entries. Exploitation likelihood is low for now: EPSS is 0.003 (79th percentile), the CVE is not in CISA KEV, and there is no public exploit or Nuclei template. However, n8n is a widely used AI agent and workflow orchestrator, the package has 244 other CVEs, and workflows that wire webhook or chat input into these nodes are exposed without authentication. The CVSS score is capped at 6.8 by high attack complexity, which reflects the need for a vulnerable workflow design rather than a hard exploit. Upgrade to 2.39.6 or 2.40.1, and audit workflows that pass untrusted input into these three nodes.
What is the risk?
Medium overall (CVSS 6.8), with high confidentiality impact and scope change, but no integrity or availability impact. Exploitation requires no privileges or user interaction, but it is only possible when a workflow binds an externally controlled value (webhook payload, form field, chat or LLM output) to a vulnerable node parameter, hence high complexity. Exploit activity is currently low: EPSS 0.003, not in KEV, no public PoC, no scanner template. The data behind SendGrid, Freshservice and ServiceNow typically contains PII and internal IT records, so the business impact of a successful query widening is higher than the score suggests. The CWE-943 flaw (improper neutralization of special elements in data query logic) is simple to weaponize once a susceptible workflow is identified.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| n8n | npm | — | No patch |
Do you use n8n? You're affected.
How severe is it?
What is the attack surface?
What should I do?
1 step1) Upgrade n8n to 2.39.6 or later on the 2.39 line, or 2.40.1 or later on the 2.40 line. 2) Inventory workflows that use the SendGrid, Freshservice or ServiceNow nodes and identify parameters bound to expressions from webhooks, forms, chat triggers or LLM outputs. 3) As a workaround until patching, validate or sanitize those inputs upstream (strict allow-lists, reject quotes and query metacharacters) and place authentication on public webhooks. 4) Apply least privilege to the SendGrid, Freshservice and ServiceNow API credentials stored in n8n so a widened query returns less data. 5) Detect abuse by reviewing execution logs for unusually large result sets, and third-party audit logs for bulk list, ticket or directory reads from the n8n service account. 6) Review the GitHub advisory GHSA-5pg9-2vqx-r6jm for fixed-version details.
What does CISA's SSVC say?
Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-103258?
n8n versions before 2.39.6 (and 2.40.0 before 2.40.1) fail to escape parameters in the SendGrid, Freshservice and ServiceNow nodes, so an attacker who controls a bound input can turn a single-record lookup into a match-all query. The result is bulk disclosure of contact lists, tickets and directory entries. Exploitation likelihood is low for now: EPSS is 0.003 (79th percentile), the CVE is not in CISA KEV, and there is no public exploit or Nuclei template. However, n8n is a widely used AI agent and workflow orchestrator, the package has 244 other CVEs, and workflows that wire webhook or chat input into these nodes are exposed without authentication. The CVSS score is capped at 6.8 by high attack complexity, which reflects the need for a vulnerable workflow design rather than a hard exploit. Upgrade to 2.39.6 or 2.40.1, and audit workflows that pass untrusted input into these three nodes.
Is CVE-2026-103258 actively exploited?
No confirmed active exploitation of CVE-2026-103258 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-103258?
1) Upgrade n8n to 2.39.6 or later on the 2.39 line, or 2.40.1 or later on the 2.40 line. 2) Inventory workflows that use the SendGrid, Freshservice or ServiceNow nodes and identify parameters bound to expressions from webhooks, forms, chat triggers or LLM outputs. 3) As a workaround until patching, validate or sanitize those inputs upstream (strict allow-lists, reject quotes and query metacharacters) and place authentication on public webhooks. 4) Apply least privilege to the SendGrid, Freshservice and ServiceNow API credentials stored in n8n so a widened query returns less data. 5) Detect abuse by reviewing execution logs for unusually large result sets, and third-party audit logs for bulk list, ticket or directory reads from the n8n service account. 6) Review the GitHub advisory GHSA-5pg9-2vqx-r6jm for fixed-version details.
What systems are affected by CVE-2026-103258?
This vulnerability affects the following AI/ML architecture patterns: agent frameworks, workflow automation, LLM tool integrations, webhook-triggered pipelines.
What is the CVSS score for CVE-2026-103258?
CVE-2026-103258 has a CVSS v3.1 base score of 6.8 (MEDIUM). The EPSS exploitation probability is 0.30%.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0036Data from Information RepositoriesAML.T0049Exploit Public-Facing ApplicationAML.T0085.001AI Agent ToolsCompliance Controls Affected
What are the technical details?
Original Advisory
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.
Exploitation Scenario
An organization runs an n8n AI support agent that receives a customer email address through a public webhook and uses the ServiceNow node to look up that customer's tickets. The attacker submits a crafted value containing a quote and a tautology that breaks out of the query literal. The node interpolates it unescaped, so the lookup becomes a match-all query, and the workflow returns, or passes to the LLM and back to the attacker, every ticket in the table. The same technique against a SendGrid contact lookup yields the full mailing list, and against a directory lookup yields employee entries useful for phishing.
Weaknesses (CWE)
CWE-943Improper Neutralization of Special Elements in Data Query LogicPrimaryCWE-943Improper Neutralization of Special Elements in Data Query LogicCWE-943 — Improper Neutralization of Special Elements in Data Query Logic: The product generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:NReferences
Timeline
Related Vulnerabilities
CVE-2026-3366310.0n8n: member role steals plaintext HTTP credentials
Same package: n8nCVE-2026-3366010.0TensorFlow: type confusion NPD in tensor conversion
Same package: n8nCVE-2026-2185810.0n8n: Input Validation flaw enables exploitation
Same package: n8nCVE-2026-274949.9n8n: security flaw enables exploitation
Same package: n8nCVE-2026-274959.9n8n: Code Injection enables RCE
Same package: n8n