fix: formidable dependency vulnerable to arbitrary#7533
Merged
jasonsaayman merged 5 commits intov1.xfrom Mar 19, 2026
Merged
Conversation
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.
Closes #6366
Summary by cubic
Updates
formidableto v3 to address the reported vulnerability (Linear 6366). Updates the test server and assertions to the new API (arrays for fields/files).Description
Summary of changes
formidablefrom^2.1.5to^3.2.4(lockfile to3.5.4).IncomingFormnamed export in the test server and tests.fieldsandfiles.Reasoning
formidable@3API changes.Additional context
formidableis a dev-only dependency used in tests/local servers.Docs
fields.foo => ['bar'],files.file1[0]).Testing
tests/setup/server.jsandtests/unit/adapters/http.test.jsto useIncomingFormand array-shaped results.formidable@3behavior.Written for commit c4fe4d1. Summary will update on new commits.