Quick answers
- Is CVE-2026-42282 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42282 being exploited in the wild.
- How severe is CVE-2026-42282?
- Medium severity, with a CVSS score of 4.3, published 8 May 2026.
- Which products and versions are affected?
- n8n-mcp (npm) < 2.47.13, SEMVER:introduced=0,fixed=2.47.13.
- Is there a fix for CVE-2026-42282?
- Yes. n8n-mcp (npm): upgrade to 2.47.13 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-42282 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-42282?
- 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.13 or later
npm install n8n-mcp@2.47.13
Technical details
n8n-mcp prior to version 2.47.13 is vulnerable to sensitive information disclosure (CWE-532) when operating in HTTP transport mode. The request dispatcher and related code paths write full JSON-RPC parameters and tool arguments to server logs before any redaction occurs. This includes sensitive data such as bearer tokens, OAuth credentials, and per-tenant API keys passed via 'n8n_manage_credentials'. An authenticated attacker or a legitimate user performing standard operations can trigger the logging of these secrets. The vulnerability is mitigated if using the 'stdio' transport mode, but in HTTP mode, the existing console-silencing layer is insufficient to prevent the data from being passed to the logger. The issue is fixed in version 2.47.13 by implementing a metadata-only summarizer for tool-call arguments.
Affected products
- czlonkowski n8n-mcp <= 2.47.12
Identifiers
- CVE-2026-42282
- GHSA-wg4g-395p-mqv3
Timeline
- 2026-04-20: patched: Version 2.47.13 released
- 2026-04-21: advisory: GitHub Security Advisory published
- 2026-05-08: disclosed: CVE published to NVD