VulnerabilityPublished 13 Aug 2026Updated 26 Oct 2026

CVE-2026-45582: n8n-MCP · Workflow telemetry sanitizer could retain partial values from URL-shaped node parameters

Affects n8n-mcpSource GCVE Database

Authoritative record:CVE-2026-45582· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.51.3 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.51.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade n8n-mcp to 2.51.3.

Affected software

Product	Affected	Fixed in
Homebrewn8n-mcp`pkg:brew/n8n-mcp`Other threats	Affected >=2.14.1 <2.51.3	Fixed in 2.51.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade n8n-mcp to version 2.51.3 or later to apply the official fix. For users unable to upgrade immediately, disable anonymous telemetry by setting any of the environment variables N8N_MCP_TELEMETRY_DISABLED, TELEMETRY_DISABLED, or DISABLE_TELEMETRY to true.

Description

A vulnerability in n8n-mcp versions from 2.14.1 up to but not including 2.51.3 allows partial fragments of URL-shaped node parameters to be retained in workflow telemetry data sent to the anonymous telemetry backend. This may expose sensitive information such as customer or tenant identifiers and short secrets embedded in query strings. The issue does not affect credentials, OAuth tokens, or workflow execution data. The vulnerability is fixed in version 2.51.3. Users unable to upgrade immediately can disable telemetry via environment variables.

Impact

Partial sensitive data embedded in URL-shaped node parameters may be exposed to operators with access to the telemetry backend. This includes customer or tenant identifiers and short secrets in query strings. Credentials, OAuth tokens, and execution data are not affected. The exposure is limited to workflow definitions sent as telemetry, potentially violating privacy expectations.

Summary

In n8n-mcp versions >=2.14.1 and <2.51.3, the workflow telemetry sanitizer fails to fully remove partial fragments of URL-shaped node parameters before sending telemetry data to the anonymous backend. This results in unintended retention of sensitive data such as customer or tenant identifiers, short secrets in query strings, and signed request parameters within stored telemetry. The flaw is limited to URL-shaped fields in workflow definitions; credentials and OAuth tokens are excluded due to separate sanitization. The issue was fixed in version 2.51.3. Operators with access to telemetry backend could read these partial sensitive fragments, violating the documented privacy boundaries.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Oct 2026, 17:15 UTC

Technical details

References

Community reviews

Related threats