Skip to content

[Snyk] Upgrade form-data from 4.0.5 to 4.0.6#13

Open
kirubakaranjayakumar wants to merge 1 commit into
mainfrom
snyk-upgrade-75dd2dd0bece681e7aab578339fd18ef
Open

[Snyk] Upgrade form-data from 4.0.5 to 4.0.6#13
kirubakaranjayakumar wants to merge 1 commit into
mainfrom
snyk-upgrade-75dd2dd0bece681e7aab578339fd18ef

Conversation

@kirubakaranjayakumar

Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to upgrade form-data from 4.0.5 to 4.0.6.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.

  • The recommended version was released 21 days ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
medium severity CRLF Injection
SNYK-JS-FORMDATA-17337015
68 Proof of Concept

Breaking Change Risk

Merge Risk: Low

Notice: This assessment is enhanced by AI.

Release notes
Package name: form-data from form-data GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade form-data from 4.0.5 to 4.0.6.

See this package in npm:
form-data

See this project in Snyk:
https://app.eu.snyk.io/org/pigs/project/581c082d-5492-4d66-b5ae-c80c24f9d394?utm_source=github-enterprise&utm_medium=referral&page=upgrade-pr
@kirubakaranjayakumar

Copy link
Copy Markdown
Author

Merge Risk: Low

This is a patch version upgrade for form-data.

Version 4.0.6 is a security update that fixes a header injection vulnerability (CWE-113). The fix involves properly escaping characters in field and file names to prevent malicious header injection.

This is a recommended security update and is not expected to introduce any breaking changes for standard usage.

Source: StepSecurity Analysis

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@cursor

cursor Bot commented Jul 4, 2026

Copy link
Copy Markdown

Bugbot is not enabled for this team, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants