Exposed Dangerous Method or Function Affecting @n8n/config package, versions <2.0.0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Exposed Dangerous Method or Function vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-N8NCONFIG-14723278
- published28 Dec 2025
- disclosed26 Dec 2025
- creditBerk Dedekargınoğlu
Introduced: 26 Dec 2025
CVE-2025-68697 (opens in a new tab)How to fix?
Upgrade @n8n/config to version 2.0.0 or higher.
Overview
Affected versions of this package are vulnerable to Exposed Dangerous Method or Function in the Code node when running in legacy JavaScript execution mode. An attacker can access or modify files on the host system with the same privileges as the application process by invoking internal helper functions from within the node. This is only exploitable if the instance is self-hosted, the legacy execution mode is enabled, and the attacker has authenticated workflow editing access.
Workaround
This vulnerability can be mitigated by:
Limiting file operations to a dedicated directory using the
N8N_RESTRICT_FILE_ACCESS_TOenvironment variableKeeping
N8N_BLOCK_FILE_ACCESS_TO_N8N_FILES=trueto block access to sensitive filesDisabling high-risk nodes (including the Code node) with
NODES_EXCLUDEif workflow editors are not fully trusted.