Authenticated file read and write via exposed helpers
Published Dec 26, 2025 · Updated Dec 26, 2025
Improper privilege management in n8n before 2.0.0 allows remote authenticated users to read and write host files through legacy Code nodes. Legacy JavaScript execution exposes internal file helper functions to workflow-authored code instead of isolating Code-node execution in a task runner. Exploitation requires a self-hosted instance, workflow-editing access, and legacy execution; file restrictions and process permissions bound the accessible paths.
Summary
What happened
Improper privilege management in n8n before 2.0.0 allows remote authenticated users to read and write host files through legacy Code nodes. Legacy JavaScript execution exposes internal file helper functions to workflow-authored code instead of isolating Code-node execution in a task runner. Exploitation requires a self-hosted instance, workflow-editing access, and legacy execution; file restrictions and process permissions bound the accessible paths.
The record
- CVE
- CVE-2025-68697
- Published
- Dec 26, 2025
- Updated
- Dec 26, 2025
- Vendor
- n8n
- Product
- n8n
- Classifications
- CWE-269, CWE-749, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 26, 2025CVE publishedPublication date reported by the CVE source.
- Dec 26, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo