Fix: Resolve form-data security vulnerability (CVE < 4.0.4)#36
Closed
Fix: Resolve form-data security vulnerability (CVE < 4.0.4)#36
Conversation
- Added npm override to force form-data to ^4.0.4 (fixes CVE in versions < 4.0.4) - n8n-workflow pins form-data to vulnerable 4.0.0 and hasn't updated in 6+ months - This override ensures we use the patched version (4.0.5) without breaking compatibility - Vulnerability: Predictable boundary generation using Math.random() instead of crypto - Reference: GHSA-fjxv-7rqg-78g4 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
📝 WalkthroughWalkthroughAdds a top-level Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
tehw0lf
added a commit
to tehw0lf/n8n-nodes-toon
that referenced
this pull request
Jan 25, 2026
Add npm overrides to force secure versions of transitive dependencies: - form-data: 4.0.0 → 4.0.5 (fixes GHSA-fjxv-7rqg-78g4, critical) - lodash: 4.17.21 → 4.17.23 (fixes GHSA-xxjr-mmjv-4gpg, moderate) These vulnerabilities exist in n8n-workflow peer dependency and cannot be fixed directly. Using overrides is safe as both updates are patch/minor versions with only security fixes. Upstream issue filed: n8n-io/n8n#24832 Reference: hostinger/api-n8n-node#36
Contributor
|
Will be solved together with - #35 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
form-datapackage (versions < 4.0.4) -- https://hostingers.atlassian.net/browse/VPS-4410 -- Security issue lasting for 6 monthsform-data@^4.0.4instead of vulnerable4.0.0Problem
Dependabot cannot automatically fix this vulnerability because:
n8n-workflow(all versions) pinsform-datato exactly4.0.0form-data@4.0.4or higherSolution
Using npm overrides to force the secure version without waiting for upstream fix. This is safe because:
Security Details
Math.random()instead of cryptoTest plan
🤖 Generated with Claude Code
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.