CVE-2026-41495: czlonkowski n8n-mcp sensitive information disclosure in logs

CVE-2026-41495 · Severity: medium · CVSS 5.3 · Published 2026-05-08

n8n-mcp is a server that allows AI assistants to interact with n8n automation tools. A security flaw in versions prior to 2.47.11 causes the server to record sensitive information, such as API keys and login tokens, into system logs even if a login attempt fails. If these logs are shared with other systems or accessible by unauthorized staff, it could lead to the theft of credentials and unauthorized access to automation workflows.

Technologies: n8n-mcp (npm). Vendors: npm.

Quick answers

Is CVE-2026-41495 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-41495 being exploited in the wild.
How severe is CVE-2026-41495?
Medium severity, with a CVSS score of 5.3, published 8 May 2026.
Which products and versions are affected?
n8n-mcp (npm) < 2.47.11, SEMVER:introduced=0,fixed=2.47.11.
Is there a fix for CVE-2026-41495?
Yes. n8n-mcp (npm): upgrade to 2.47.11 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41495 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-41495?
Check whether you run n8n-mcp (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • n8n-mcp (npm): upgrade to 2.47.11 or later
    npm install n8n-mcp@2.47.11

Technical details

n8n-mcp prior to version 2.47.11 is vulnerable to sensitive information disclosure via log files (CWE-532). When running in HTTP transport mode, the server logs request metadata for all incoming POST requests to the /mcp endpoint, including those that fail authentication with a 401 Unauthorized status. This logging includes sensitive headers such as 'Authorization' (bearer tokens) and 'x-n8n-key' (API keys), as well as JSON-RPC request payloads. An attacker can intentionally send requests containing sensitive data to populate logs that may be accessible via shared storage, SIEM pipelines, or monitoring tools. The issue is patched in version 2.47.11; users can also mitigate the risk by switching to stdio transport mode.

Affected products

  • czlonkowski n8n-mcp <= 2.47.10

Identifiers

  • CVE-2026-41495
  • GHSA-pfm2-2mhg-8wpx

Timeline

  • 2026-04-16: patched: Version 2.47.11 released
  • 2026-04-20: advisory: GitHub Security Advisory published
  • 2026-05-08: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.