Summary
Path traversal in Node-Red
Workarounds
The vulnerability applies only to the Projects feature which is not enabled by default in Node-RED.
The primary workaround is not give untrusted users read access to the Node-RED editor.
For more information
If you have any questions or comments about this advisory:
- Email us at [email protected]
Acknowledgements
Thanks to the Tencent Woodpecker Security Team for disclosing this vulnerability.
Impact
This vulnerability allows arbitrary path traversal via the Projects API.
If the Projects feature is enabled, a user with projects.read permission is able to access any file via the Projects API.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The issue has been patched in Node-RED 1.2.8
Frequently Asked Questions
- What is CVE-2021-21298? CVE-2021-21298 is a low-severity path traversal vulnerability in @node-red/runtime (npm), affecting versions < 1.2.8. It is fixed in 1.2.8. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- Which versions of @node-red/runtime are affected by CVE-2021-21298? @node-red/runtime (npm) versions < 1.2.8 is affected.
- Is there a fix for CVE-2021-21298? Yes. CVE-2021-21298 is fixed in 1.2.8. Upgrade to this version or later.
- Is CVE-2021-21298 exploitable, and should I be worried? Whether CVE-2021-21298 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2021-21298 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2021-21298? Upgrade
@node-red/runtimeto 1.2.8 or later.