CVE-2026-41495
Full vulnerability record from the local CVENow database.
Description
n8n-MCP is an MCP server that provides AI assistants access to n8n node documentation, properties, and operations. Prior to version 2.47.11, when n8n-mcp runs in HTTP transport mode, incoming requests to the POST /mcp endpoint had their request metadata written to server logs regardless of the authentication outcome. 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 from the Authorization header, per-tenant API keys from the, x-n8n-key header in multi-tenant setups, JSON-RPC request payloads sent to the MCP endpoint. Access control itself was not bypassed — unauthenticated requests were correctly rejected with 401 Unauthorized — but sensitive values from those rejected requests could still be persisted in logs. This issue has been patched in version 2.47.11.
View original CVE JSON
{
"id": "CVE-2026-41495",
"sourceIdentifier": "[email protected]",
"published": "2026-05-08T20:16:30.323",
"lastModified": "2026-10-26T18:10:00.173",
"vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "n8n-MCP is an MCP server that provides AI assistants access to n8n node documentation, properties, and operations. Prior to version 2.47.11, when n8n-mcp runs in HTTP transport mode, incoming requests to the POST /mcp endpoint had their request metadata written to server logs regardless of the authentication outcome. 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 from the Authorization header, per-tenant API keys from the, x-n8n-key header in multi-tenant setups, JSON-RPC request payloads sent to the MCP endpoint. Access control itself was not bypassed — unauthenticated requests were correctly rejected with 401 Unauthorized — but sensitive values from those rejected requests could still be persisted in logs. This issue has been patched in version 2.47.11."
},
{
"lang": "es",
"value": "n8n-MCP es un servidor MCP que proporciona a los asistentes de IA acceso a la documentación, propiedades y operaciones de los nodos n8n. Antes de la versión 2.47.11, cuando n8n-mcp se ejecuta en modo de transporte HTTP, las solicitudes entrantes al endpoint POST /mcp tenían sus metadatos de solicitud escritos en los registros del servidor independientemente del resultado de la autenticación. En implementaciones donde los registros se recopilan, se reenvían a sistemas externos o son visibles fuera del límite de confianza de la solicitud (almacenamiento de registros compartido, pipelines SIEM, acceso de soporte/operaciones), esto puede resultar en la divulgación de: tokens de portador del encabezado de autorización, claves API por inquilino del encabezado x-n8n-key en configuraciones multi-inquilino, cargas útiles de solicitud JSON-RPC enviadas al endpoint MCP. El control de acceso en sí mismo no fue eludido - las solicitudes no autenticadas fueron correctamente rechazadas con 401 No autorizado - pero los valores sensibles de esas solicitudes rechazadas aún podían persistir en los registros. Este problema ha sido parcheado en la versión 2.47.11."
}
],
"affected": [
{
"source": "[email protected]",
"affectedData": [
{
"vendor": "czlonkowski",
"product": "n8n-mcp",
"versions": [
{
"version": "< 2.47.11",
"status": "affected"
}
]
}
]
}
],
"metrics": {
"cvssMetricV31": [
{
"source": "[email protected]",
"type": "Secondary",
"cvssData": {
"version": "3.1",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"attackVector": "NETWORK",
"attackComplexity": "LOW",
"privilegesRequired": "NONE",
"userInteraction": "NONE",
"scope": "UNCHANGED",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"availabilityImpact": "NONE"
},
"exploitabilityScore": 3.9,
"impactScore": 1.4
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"timestamp": "2026-05-13T17:17:26.422382Z",
"id": "CVE-2026-41495",
"options": [
{
"exploitation": "none"
},
{
"automatable": "yes"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"version": "2.0.3"
}
}
]
},
"weaknesses": [
{
"source": "[email protected]",
"type": "Secondary",
"description": [
{
"lang": "en",
"value": "CWE-532"
}
]
}
],
"configurations": [
{
"nodes": [
{
"operator": "OR",
"negate": false,
"cpeMatch": [
{
"vulnerable": true,
"criteria": "cpe:2.3:a:n8n-mcp:n8n-mcp:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2.47.11",
"matchCriteriaId": "BACF38A0-0100-4102-BE5A-43C672B654AE"
}
]
}
]
}
],
"references": [
{
"url": "https://github.com/czlonkowski/n8n-mcp/releases/tag/v2.47.11",
"source": "[email protected]",
"tags": [
"Product",
"Release Notes"
]
},
{
"url": "https://github.com/czlonkowski/n8n-mcp/security/advisories/GHSA-pfm2-2mhg-8wpx",
"source": "[email protected]",
"tags": [
"Mitigation",
"Vendor Advisory"
]
}
]
}