VulnerabilityPublished 13 Aug 2026Updated 26 Oct 2026

CVE-2026-41495: n8n-MCP Logs Sensitive Request Data on Unauthorized /mcp Requests

Affects n8n-mcpSource GCVE Database

Authoritative record:CVE-2026-41495· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.47.11 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.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.11

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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.11.

Affected software

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

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.47.11 or later, where the issue is fixed. If immediate upgrade is not possible, restrict network access to the HTTP port using firewalls, reverse proxies, or VPNs to limit access to trusted clients only. Alternatively, switch to stdio transport mode (MCP_MODE=stdio), which does not expose an HTTP interface and is not affected by this vulnerability.

Description

A vulnerability in n8n-mcp versions 2.14.1 through 2.47.10 allows sensitive request data to be logged on unauthorized POST /mcp HTTP requests. This includes bearer tokens, per-tenant API keys, and JSON-RPC payloads. Although unauthorized requests are rejected, sensitive information is still recorded in server logs, potentially exposing it if logs are accessible outside the trusted boundary. The issue affects deployments using HTTP transport mode and is fixed in version 2.47.11.

Impact

Sensitive authentication tokens and request payloads can be exposed through server logs if those logs are accessible beyond the request trust boundary, such as in shared log storage, SIEM systems, or by support and operations personnel. This exposure does not bypass access controls since unauthorized requests are rejected, but the persistence of sensitive data in logs increases the risk of credential leakage and unauthorized access if logs are improperly handled.

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