VulnerabilityPublished 13 Aug 2026Updated 26 Oct 2026

CVE-2026-42282: n8n-MCP · Sensitive MCP tool-call arguments logged on authenticated requests in HTTP mode

Affects n8n-mcpSource GCVE Database

Authoritative record:CVE-2026-42282· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium : upgrade to 2.47.13 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

4.3Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 8 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.47.13.

Affected software

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

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

AI-suggested

A patch is available in n8n-mcp version 2.47.13 that removes the logging of sensitive tool-call argument values by summarizing arguments without recording raw data. Users should upgrade to version 2.47.13 or later. If immediate upgrade is not possible, restrict access to the HTTP port to trusted clients only, restrict access to server logs to prevent unauthorized viewing, or switch to stdio transport mode (MCP_MODE=stdio), which does not log sensitive data in this manner.

Description

n8n-mcp versions 2.14.1 up to but not including 2.47.13 running in HTTP transport mode log sensitive tool-call arguments including credential material such as bearer tokens, OAuth credentials, API keys, and webhook authentication headers. This logging occurs before any redaction, potentially exposing secrets in server logs accessible beyond the request trust boundary. The vulnerability requires authentication and is mitigated in stdio transport mode. A fix is available in version 2.47.13 that prevents logging sensitive values by summarizing arguments without recording raw data.

Impact

Sensitive credential material including bearer tokens, OAuth credentials, per-tenant API keys, webhook authentication headers, and arbitrary secret-bearing payloads can be exposed in server logs. If logs are collected, forwarded, or accessible outside the request trust boundary, this can lead to unauthorized disclosure of secrets. The vulnerability requires authentication, so unauthenticated attackers cannot exploit it. The impact is limited to confidentiality loss of sensitive information in logs; integrity and availability are not affected.

Summary

The n8n-mcp component, when operating in HTTP transport mode, logs full arguments and JSON-RPC parameters of authenticated MCP tool-call requests before redaction. This includes sensitive credential data such as bearer tokens, OAuth credentials, and API keys passed through the n8n_manage_credentials tool or other MCP tools. The vulnerability is classified as CWE-532 (Insertion of Sensitive Information into Log File) and has a CVSS 3.1 score of 4.3 (Medium). It affects versions >=2.14.1 and <2.47.13. The issue requires valid authentication tokens to exploit, limiting unauthenticated access. The vulnerability is fixed in version 2.47.13 by routing tool-call arguments through a metadata-only summarizer that records only types and keys, never raw values. Workarounds include restricting HTTP port access, limiting log access, or switching to stdio transport mode which is unaffected.

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