fix: [form-data] Upgrade form-data from 2.3.3 to 2.5.4 to resolve CVE-2025-7783 - #281
Open
hannahhuh-cog wants to merge 1 commit into
Open
hannahhuh-cog wants to merge 1 commit into
hannahhuh-cog wants to merge 1 commit into
Conversation
Co-Authored-By: Hannah Huh <hannah.huh@cognition.ai>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
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
Forces the transitive dependency
form-data2.3.3->2.5.4via an npmoverridesentry to remediate a Critical vulnerability flagged by the scheduled Snyk SCA scan.form-datais pulled in throughtap > coveralls > request@2.88.0, andrequestpinsform-data@~2.3.2, so a plain relock cannot reach the fixed version; Snyk's only alternative was upgradingtap11 -> 18 (a major, breaking bump).Vulnerability
Math.random()for multipart boundary generation)form-data@2.3.3introduced throughtap@11.1.5 > coveralls@3.0.9 > request@2.88.0 > form-data@2.3.32.5.4(also 3.0.4, 4.0.4)Risk: predictable multipart boundaries allow an attacker who can observe other
Math.random()outputs to inject extra parameters into multipart requests.Verification: lockfile and runtime
form-databoth2.5.4. Lockfile also gains 2.5.4's own small dependency subtree (es-set-tostringtag,hasown, etc.).Snyk scan reference: Snyk MCP SCA scan of
COG-GTM/nodejs-goofon 2026-09-14 (org9e26acce-22c7-4efc-b470-21d9587f49fe).Devin-Org: engineering
Link to Devin session: https://app.devin.ai/sessions/387468bb0c6d4d6dbb7183fbbb24385f
Open in Devin Desktop: https://app.devin.ai/desktop/session/387468bb0c6d4d6dbb7183fbbb24385f?variant=devin
Requested by: @hannahhuh-cog