CVE-2026-42282: n8n-MCP Sensitive MCP Tool-call Arguments Logged Vulnerability

MODERATE
Advisory Identifier: GHSA-wg4g-395p-mqv3
CVSS 4.3
CWE-532
Published
Advisory Summary

CVE-2026-42282 is a MODERATE (CVSS 4.3) sensitive mcp tool-call arguments logged vulnerability (CWE-532: Insertion of Sensitive Information into Log File) affecting n8n-MCP libraries in the npm ecosystem. The issue involves sensitive mcp tool-call arguments logged on authenticated requests in http mode. Remediation is available by upgrading affected packages to version 2.47.13.

CVE-2026-42282 at a Glance

CVE Identifier CVE-2026-42282
GHSA Identifier GHSA-wg4g-395p-mqv3
Severity MODERATE
CVSS v3.1 Base Score 4.3
CWE Classification CWE-532: Insertion of Sensitive Information into Log File
Affected Product n8n-MCP
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 4.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-42282

To remediate this vulnerability, upgrade all affected n8n-MCP dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

n8n-mcp fixed: 2.47.13
npm install n8n-mcp@2.47.13
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls n8n-mcp

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-42282, inspect your project dependencies using npm:

npm ls n8n-mcp

Analyze the terminal output to locate any version of n8n-MCP in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.47.13), your application is affected.

Note: The npm ls n8n-mcp command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-532: Insertion of Sensitive Information into Log File, where the product writes sensitive information to a log file. In n8n-MCP, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact When `n8n-mcp` runs in HTTP transport mode, authenticated MCP `tools/call` requests had their full arguments and JSON-RPC params written to server logs by the request dispatcher and several sibling code paths before any redaction. When a tool call carries credential material — most notably `n8n_manage_credentials.data` — the raw values can be persisted in logs. In deployments where logs are collected, forwarded to external systems, or viewable outside the request trust boundary (shared log storage, SIEM pipelines, support/ops access), this can result in disclosure of: - bearer tokens and OAuth credentials sent through `n8n_manage_credentials` - per-tenant API keys and webhook auth headers embedded in tool arguments - arbitrary secret-bearing payloads passed to any MCP tool The issue requires authentication (`AUTH_TOKEN` accepted by the server), so unauthenticated callers cannot trigger it; the runtime exposure is also reduced by an existing console-silencing layer in HTTP mode, but that layer is fragile and the values are still constructed and passed into the logger. The fix removes the leak at the source. Impact category: **CWE-532** (Insertion of Sensitive Information into Log File). CVSS 3.1 score: **4.3 Medium** (`AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`). ### Affected Deployments running n8n-mcp **v2.47.12 or earlier** in HTTP transport mode (`MCP_MODE=http`). The stdio transport short-circuits the relevant log calls and is not affected in practice. ### Patched **v2.47.13** and later. - npm: `npx n8n-mcp@latest` (or pin to `>= 2.47.13`) - Docker: `docker pull ghcr.io/czlonkowski/n8n-mcp:latest` The patch routes tool-call arguments through a metadata-only summarizer (`summarizeToolCallArgs`) that records type, top-level key names, and approximate size — never values. The same pattern was adopted earlier for HTTP request bodies in GHSA-pfm2-2mhg-8wpx. ### Workarounds If developers cannot upgrade immediately: - Restrict access to the HTTP port (firewall, reverse proxy, or VPN) so only trusted clients can authenticate. - Restrict access to server logs (no shared SIEM ingestion, no support read-only access) until the upgrade lands. - Switch to stdio transport (`MCP_MODE=stdio`, the default for CLI invocation), which has no HTTP surface and short-circuits the affected log calls. ### Credit n8n-MCP thanks [@Mirr2](https://github.com/Mirr2) (Organization / Jormungandr) for reporting this issue.

CVE-2026-42282 Affected n8n-MCP Versions

1 component(s)
Fixed Versions:
2.47.13
Product / Package Ecosystem Affected Versions Fixed Version
n8n-mcp
npm
< 2.47.13
2.47.13

References

Frequently Asked Questions

What is CVE-2026-42282?
CVE-2026-42282 is a security vulnerability in n8n-MCP involving Sensitive MCP tool-call arguments logged on authenticated requests in HTTP mode under CWE-532: Insertion of Sensitive Information into Log File.
Which n8n-MCP versions are affected?
Affected versions include releases prior to 2.47.13 across affected packages: n8n-mcp.
What version fixes CVE-2026-42282?
Upgrading to 2.47.13 (or the latest patched release for your respective branch) resolves the vulnerability.
Is n8n-mcp affected?
Yes, n8n-mcp is affected in releases prior to 2.47.13. Upgrade your dependency to 2.47.13 or later.
What is the CVSS score of CVE-2026-42282?
CVE-2026-42282 has a CVSS v3.1 base score of 4.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2026-42282?
CVE-2026-42282 is classified under CWE-532: Insertion of Sensitive Information into Log File (The product writes sensitive information to a log file.).
How can I check npm dependencies for CVE-2026-42282?
Run the dependency tree command: 'npm ls n8n-mcp'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-wg4g-395p-mqv3",
  "modified" : "2026-05-13T13:34:59Z",
  "published" : "2026-04-25T23:35:28Z",
  "aliases" : [ "CVE-2026-42282" ],
  "summary" : "n8n-MCP: Sensitive MCP tool-call arguments logged on authenticated requests in HTTP mode",
  "details" : "### Impact\n\nWhen `n8n-mcp` runs in HTTP transport mode, authenticated MCP `tools/call` requests had their full arguments and JSON-RPC params written to server logs by the request dispatcher and several sibling code paths before any redaction. When a tool call carries credential material — most notably `n8n_manage_credentials.data` — the raw values can be persisted in logs.\n\nIn deployments where logs are collected, forwarded to external systems, or viewable outside the request trust boundary (shared log storage, SIEM pipelines, support/ops access), this can result in disclosure of:\n\n- bearer tokens and OAuth credentials sent through `n8n_manage_credentials`\n- per-tenant API keys and webhook auth headers embedded in tool arguments\n- arbitrary secret-bearing payloads passed to any MCP tool\n\nThe issue requires authentication (`AUTH_TOKEN` accepted by the server), so unauthenticated callers cannot trigger it; the runtime exposure is also reduced by an existing console-silencing layer in HTTP mode, but that layer is fragile and the values are still constructed and passed into the logger. The fix removes the leak at the source.\n\nImpact category: **CWE-532** (Insertion of Sensitive Information into Log File). CVSS 3.1 score: **4.3 Medium** (`AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`).\n\n### Affected\n\nDeployments running n8n-mcp **v2.47.12 or earlier** in HTTP transport mode (`MCP_MODE=http`). The stdio transport short-circuits the relevant log calls and is not affected in practice.\n\n### Patched\n\n**v2.47.13** and later.\n\n- npm: `npx n8n-mcp@latest` (or pin to `>= 2.47.13`)\n- Docker: `docker pull ghcr.io/czlonkowski/n8n-mcp:latest`\n\nThe patch routes tool-call arguments through a metadata-only summarizer (`summarizeToolCallArgs`) that records type, top-level key names, and approximate size — never values. The same pattern was adopted earlier for HTTP request bodies in GHSA-pfm2-2mhg-8wpx.\n\n### Workarounds\n\nIf developers cannot upgrade immediately:\n\n- Restrict access to the HTTP port (firewall, reverse proxy, or VPN) so only trusted clients can authenticate.\n- Restrict access to server logs (no shared SIEM ingestion, no support read-only access) until the upgrade lands.\n- Switch to stdio transport (`MCP_MODE=stdio`, the default for CLI invocation), which has no HTTP surface and short-circuits the affected log calls.\n\n### Credit\n\nn8n-MCP thanks [@Mirr2](https://github.com/Mirr2) (Organization / Jormungandr) for reporting this issue.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n-mcp"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.47.13"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/czlonkowski/n8n-mcp/security/advisories/GHSA-wg4g-395p-mqv3"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-42282"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/czlonkowski/n8n-mcp/commit/59b665bda36797823df238aeaf20adb862c9f451"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/czlonkowski/n8n-mcp"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/czlonkowski/n8n-mcp/releases/tag/v2.47.13"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-532" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-25T23:35:28Z",
    "nvd_published_at" : "2026-05-08T20:16:31Z"
  }
}