CVEReports
CVEReports

Automated vulnerability intelligence platform. Comprehensive reports for high-severity CVEs generated by AI.

Product

  • Home
  • Sitemap
  • RSS Feed

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CVEReports. All rights reserved.

Made with love by Amit Schendel & Alon Barad



GHSA-WG4G-395P-MQV3

GHSA-WG4G-395P-MQV3: Cleartext Logging of Sensitive Tool-Call Arguments in n8n-mcp

Alon Barad
Alon Barad
Software Engineer

Apr 28, 2026·6 min read·48 visits

Executive Summary (TL;DR)

n8n-mcp logs sensitive tool-call arguments in cleartext when running in HTTP mode. Update to version 2.47.3 to remove the vulnerable logging configuration.

The n8n-mcp npm package prior to version 2.47.3 contains an information disclosure vulnerability when operating in HTTP mode. The server explicitly logs incoming JSON-RPC request bodies, which exposes sensitive tool-call arguments, including API keys and internal data, to application logs in cleartext.

Vulnerability Overview

The n8n-mcp package provides a Model Context Protocol (MCP) server implementation for interacting with n8n workflows. When the server is configured to operate in HTTP mode (Single Session), it handles incoming JSON-RPC requests from AI assistants and other clients. The implementation of the HTTP handler inadvertently records the entire parsed request body to standard logging facilities.

This behavior introduces a CWE-532 (Insertion of Sensitive Information into Log File) vulnerability. The Model Context Protocol uses the params field of the JSON-RPC request to transmit operational data, which frequently includes API keys, authentication tokens, private infrastructure URLs, and sensitive user input destined for workflow processing.

By persisting this cleartext data to standard output or log files, the application breaks the confidentiality boundary of the encrypted HTTP transport. Log management systems, which typically possess less stringent access controls than production databases or secret managers, will permanently index these credentials.

Root Cause Analysis

The root cause exists within the SingleSessionHTTPServer class located in the http-server-single-session.ts file. This component is responsible for intercepting and routing HTTP requests containing MCP tool calls. When a request is authenticated and processed, the server logs an informational message indicating that a request is being handled.

The developers explicitly constructed the log object by referencing the params attribute of the incoming JSON body. Unlike HTTP headers, where developers frequently apply redaction filters, the JSON-RPC payload was treated as safe diagnostic data. The application did not differentiate between generic operational arguments and sensitive authentication material passed within the same object structure.

The logging instruction executes synchronously upon request receipt. Because the log aggregator records the raw properties of the req.body object, any AI assistant executing a tool call that requires secrets will automatically inject those secrets into the application's logging stream. The vulnerability is fundamentally a failure to sanitize untrusted structured data before passing it to an I/O subsystem.

Code Analysis

The vulnerability stems from an explicit logging call in the HTTP request handler. The code constructs an object using properties directly extracted from the incoming request body, notably including the params field.

// PRE-PATCH (Vulnerable)
logger.info('handleRequest: Processing MCP request', {
    method: req.body?.method,
    params: req.body?.params,  // Vulnerable parameter logging
    id: req.body?.id
});

The patch implemented in version 2.47.3 (commit 643c98bcf7663fe8f08f6dfd21d2ddeb56634387) removes the params field from the logging output entirely. This fix directly addresses the CodeQL js/clear-text-logging alert by dropping the untrusted data from the diagnostic output.

// POST-PATCH (Fixed)
logger.info('handleRequest: Processing MCP request', {
    method: req.body?.method,
    id: req.body?.id           // Safe attributes retained
});

This remediation is complete for this specific code path. By strictly limiting the logged fields to operational metadata (method and id), the developers ensure that user-provided arguments cannot inadvertently bleed into the logging infrastructure. This approach is superior to implementing a regex-based redaction filter, which is prone to bypasses and maintenance overhead.

Exploitation & Threat Modeling

Exploitation of this vulnerability requires access to the application's logging infrastructure rather than direct network access to the MCP server. The attack is passive; the threat actor monitors log files, container stdout streams, or centralized logging platforms (such as ELK, Splunk, or Datadog) to extract harvested credentials.

A typical exploitation scenario involves an attacker who has compromised a secondary system or holds internal privileges that grant log read access. When a legitimate user interacts with an AI assistant to trigger an n8n workflow, the assistant generates a tool call.

The resulting log entry provides the attacker with structured, easily parseable cleartext credentials. A sample log entry appears as follows: info: handleRequest: Processing MCP request { method: 'tools/call', params: { name: 'n8n_run_workflow', arguments: { apiKey: 'SECRET_VALUE' } }, id: 1 }. Attackers can utilize automated scripts to continuously scrape these logs for regex patterns matching API keys or session tokens.

Impact Assessment

The primary impact is a severe loss of confidentiality for systems integrating with the n8n-mcp service. API keys, database connection strings, and user credentials passed as arguments to n8n workflows are routinely exposed. This exposure facilitates horizontal privilege escalation, allowing an attacker to authenticate to internal services bypassing normal access controls.

The severity of the impact depends heavily on the deployment environment's log retention and access policies. In environments where logs are forwarded to shared dashboards or retained indefinitely, the window of exposure is significant. Developers often assume that authenticated HTTP traffic is secure, making the silent leakage into backend logs particularly dangerous.

Furthermore, this logging behavior violates standard compliance frameworks (such as SOC2, PCI-DSS, and GDPR) which strictly prohibit the cleartext storage of sensitive authentication material or personally identifiable information (PII). Organizations discovering this vulnerability must assume that any credentials used in conjunction with the MCP server prior to patching have been compromised.

Remediation & Mitigation

The primary remediation is to upgrade the n8n-mcp package to version 2.47.3 or later. This version implements the necessary code changes to prevent the logging of the params object. Developers should verify the installed version by inspecting the package.json lockfiles and executing npm update n8n-mcp.

Applying the patch does not secure credentials that have already been written to log files. Organizations must identify the location of their logging data and execute a purge of historical logs containing the handleRequest: Processing MCP request string. If targeted log deletion is not feasible, log rotation policies should be aggressively accelerated to drop the vulnerable historical data.

Finally, all security tokens, API keys, and passwords that were transmitted to the MCP server during the vulnerable period must be considered compromised and rotated immediately. Relying solely on patching the library without rotating exposed credentials leaves the system vulnerable to exploitation using historical log data.

Official Patches

GitHub Advisory DatabaseOfficial GitHub Security Advisory
n8n-mcpFix Commit in Repository

Fix Analysis (1)

Technical Appendix

CVSS Score
5.3/ 10
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected Systems

n8n-mcp npm packageModel Context Protocol (MCP) server implementationsLog aggregation and monitoring infrastructure

Affected Versions Detail

Product
Affected Versions
Fixed Version
n8n-mcp
n8n-mcp maintainers
< 2.47.32.47.3
AttributeDetail
Vulnerability TypeCWE-532: Insertion of Sensitive Information into Log File
Attack VectorLocal / Log Access
ImpactHigh Confidentiality Loss
Exploit StatusPassive Information Disclosure
CVSS Score5.3 (Moderate)
Affected Componentn8n-mcp < 2.47.3

MITRE ATT&CK Mapping

T1552Credentials In Files
Credential Access
T1552.001Credentials In Files: Local Files
Credential Access
CWE-532
Insertion of Sensitive Information into Log File

The software records sensitive information into a log file, which may allow attackers to extract credentials or private data.

Vulnerability Timeline

Vulnerability patched via commit 643c98bc.
2026-04-08
GitHub Security Advisory published.
2026-04-08

References & Sources

  • [1]GHSA-wg4g-395p-mqv3: Sensitive MCP tool-call arguments logged on authenticated requests in HTTP mode
  • [2]n8n-mcp Fix Commit
  • [3]n8n-mcp Package Repository

Attack Flow Diagram

Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

More Reports

•10 minutes ago•CVE-2026-69138
6.5

CVE-2026-69138: Authorization Bypass Through User-Controlled Key and Missing Authorization in djangocms-versioning

An authorization bypass and broken object-level access control vulnerability exists in djangocms-versioning prior to version 2.6.1. The check_discard and check_edit_redirect condition pipelines on the Version model omitted the user_can_change permission predicate. Because the corresponding administrative views retrieve target versions directly by their URL primary key and depend entirely on these condition pipelines for object-level access control, authenticated staff users without per-object change permissions can permanently delete draft versions or spawn new draft versions from published content.

Alon Barad
Alon Barad
1 views•10 min read
•about 1 hour ago•CVE-2026-69131
4.3

CVE-2026-69131: Missing Authorization in django-filer Bulk Deletion Admin Action

A missing authorization vulnerability exists in django-filer versions prior to 3.5.0 when the optional per-folder permission system (FILER_ENABLE_PERMISSIONS) is enabled. The bulk delete admin action (delete_files_or_folders) verifies global Django model-level deletion permissions but fails to enforce object-level FolderPermission edit checks. Consequently, an authenticated staff user holding model-level delete rights can delete files, folders, and directory trees from folders where their access has been explicitly restricted to read-only via FolderPermission.

Alon Barad
Alon Barad
2 views•9 min read
•about 2 hours ago•CVE-2026-75506
6.6

CVE-2026-75506: Second-Order OS Command Injection in OliveTin shellAfterCompleted Hook

CVE-2026-75506 (GHSA-vc6p-m6vx-6cwq) is a second-order OS command injection vulnerability in OliveTin affecting versions 3000.0.0 prior to 3000.18.1. The post-execution hook mechanism, shellAfterCompleted, interpolates runtime execution outputs and username variables directly into a shell command string passed to sh -c without validation. When an action emits untrusted output containing shell metacharacters, those metacharacters break out of the intended syntax and execute arbitrary OS commands under the context of the OliveTin service process.

Alon Barad
Alon Barad
3 views•10 min read
•about 3 hours ago•CVE-2026-71481
7.5

CVE-2026-71481: Cryptographic Signature Verification Bypass in ALTCHA PHP Library

CVE-2026-71481 (GHSA-82w8-65qw-gch6) is a cryptographic signature verification bypass (CWE-347) in the altcha-org/altcha PHP library affecting versions 2.0.0 through 2.0.2. Due to a flawed conditional check in the verifySolution method, omitting the signature field from a submitted challenge payload causes the server to skip HMAC verification entirely, even when a server-side HMAC secret is configured. Unauthenticated remote attackers can exploit this flaw to self-issue low-difficulty Proof-of-Work challenges, solve them with trivial effort, and bypass CAPTCHA controls.

Alon Barad
Alon Barad
4 views•10 min read
•about 6 hours ago•CVE-2026-61618
6.9

CVE-2026-61618: Improper Input Validation of KZG Accumulator Limbs in snark-verifier

CVE-2026-61618 (GHSA-265x-v3qf-ff6p) is an improper input validation vulnerability (CWE-20) in Axiom Crypto's snark-verifier library prior to version 0.2.5. The library decodes KZG accumulator public-instance limbs without enforcing canonical bit-width bounds prior to elliptic curve coordinate reconstruction. In the Ethereum Virtual Machine (EVM) loader path, the generated Yul bytecode validates that reconstructed affine coordinates lie on the elliptic curve, but fails to verify that the constituent limbs respect their allocated bit-widths, allowing non-canonical proof representations. In the native Rust execution path, accumulator decoding relies on unchecked assertions and unwraps, allowing malformed public instances to trigger an unhandled process panic.

Amit Schendel
Amit Schendel
4 views•12 min read
•about 7 hours ago•CVE-2026-63496
7.8

CVE-2026-63496: OS Command Injection in @augment-vir/node grep() Helper

An OS command injection vulnerability (CWE-78) exists in the @augment-vir/node package prior to version 31.73.5. The grep() utility function builds a shell command string by interpolating caller-supplied search patterns inside double quotes and executes the string through bash via runShellCommand(). Because bash evaluates command substitution expressions inside double-quoted strings, an attacker controlling the search pattern input can execute arbitrary OS commands with the privileges of the Node.js runtime.

Alon Barad
Alon Barad
4 views•8 min read