VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

form-data: vulnerability history, versions and safety

form-data is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 39 releases, from Jul 2025 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 15 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all form-data vulnerabilities

Vulert verdict on form-data 4.0.6 i

Updated on 23 Oct 2026

Good news: 4.0.6, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 76/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

What to do: Stay on 4.0.6 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.0.6 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.0.6 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 1 in the last year i
  • Latest disclosure 15 Jun 2026 i
  • Highest CVSS 9.4 i
  • With no published fix 0 i
  • Depended on by 268,947 packages i
  • Stars 2,356 i
  • OpenSSF scorecard 3/10 i
  • Last release 4 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for form-data, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.5.6 12 Jun 2026 none MIT — Details →
3.0.5 12 Jun 2026 none MIT — Details →
4.0.6 12 Jun 2026 none MIT — Details →
4.0.5 17 Nov 2025 none MIT — Details →
2.5.5 18 Jul 2025 H1 MIT Yes Details →
2.5.4 17 Jul 2025 H1 MIT Yes Details →
3.0.4 17 Jul 2025 none MIT — Details →
4.0.4 17 Jul 2025 none MIT — Details →
4.0.3 05 Jun 2025 none MIT — Details →
4.0.2 14 Feb 2025 none MIT — Details →
3.0.3 14 Feb 2025 none MIT — Details →
2.5.3 14 Feb 2025 C1 H1 MIT Yes Details →
4.0.1 10 Oct 2024 none MIT — Details →
3.0.2 10 Oct 2024 none MIT — Details →
2.5.2 10 Oct 2024 C1 H1 MIT Yes Details →
4.0.0 15 Feb 2021 none MIT — Details →
3.0.1 15 Feb 2021 none MIT — Details →
3.0.0 06 Nov 2019 none MIT — Details →
2.5.1 29 Aug 2019 C1 H1 MIT Yes Details →
2.5.0 04 Jul 2019 C1 H1 MIT Yes Details →
2.4.0 19 Jun 2019 C1 H1 MIT Yes Details →
2.3.3 17 Oct 2018 C1 H1 MIT Yes Details →
2.3.2 14 Feb 2018 C1 H1 MIT Yes Details →
2.3.2-rc1 12 Feb 2018 C1 H1 MIT Yes Details →
2.3.1 24 Aug 2017 C1 H1 MIT Yes Details →
2.2.0 11 Jun 2017 C1 H1 MIT Yes Details →
2.1.4 09 Apr 2017 C1 H1 MIT Yes Details →
2.1.2 08 Nov 2016 C1 H1 MIT Yes Details →
2.1.1 04 Oct 2016 C1 H1 MIT Yes Details →
2.1.0 25 Sep 2016 C1 H1 MIT Yes Details →
2.0.0 17 Sep 2016 C1 H1 MIT Yes Details →
1.0.1 26 Aug 2016 C1 H1 MIT Yes Details →
1.0.0 26 Aug 2016 C1 H1 MIT Yes Details →
1.0.0-rc4 15 Mar 2016 C1 H1 MIT Yes Details →
1.0.0-rc3 30 Jul 2015 C1 H1 MIT Yes Details →
1.0.0-rc2 22 Jul 2015 C1 H1 MIT Yes Details →
1.0.0-rc1 13 Jun 2015 C1 H1 MIT Yes Details →
0.2.0 06 Dec 2014 C1 H1 MIT Yes Details →
0.1.4 24 Jun 2014 C1 H1 MIT Yes Details →
0.1.3 02 Jun 2014 C1 H1 MIT Yes Details →
0.1.2 03 Oct 2013 C1 H1 MIT Yes Details →
0.1.1 22 Aug 2013 C1 H1 MIT Yes Details →
0.1.0 08 Jul 2013 C1 H1 MIT Yes Details →
0.0.10 09 May 2013 C1 H1 MIT Yes Details →
0.0.9 29 Apr 2013 C1 H1 MIT Yes Details →
0.0.8 21 Apr 2013 C1 H1 MIT Yes Details →
0.0.7 10 Feb 2013 C1 H1 MIT Yes Details →
0.0.6 08 Jan 2013 C1 H1 MIT Yes Details →
0.0.5 05 Dec 2012 C1 H1 MIT Yes Details →
0.0.4 06 Sep 2012 C1 H1 MIT Yes Details →
0.0.3 10 Aug 2012 C1 H1 MIT Yes Details →
0.0.2 02 Jul 2012 C1 H1 MIT Yes Details →
0.0.0 16 May 2011 C1 H1 MIT Yes Details →

All 53 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for form-data

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2025-7783: form-data Package Boundary Value Vulnerability 9.4 critical 2.5.4 21 Jul 2025
CVE-2026-12143: form-data CRLF Injection Vulnerability 7.5 high 2.5.6 15 Jun 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About form-data

Is form-data safe to use?

Vulert records 2 vulnerabilities for form-data in npm: 1 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is form-data's Vulert package health score?

Vulert scores form-data 76/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of form-data affected?

No. 4.0.6, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of form-data should I use?

4.0.6 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does form-data have?

2 vulnerabilities are recorded for form-data in the npm ecosystem: 1 critical, 1 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new form-data vulnerabilities disclosed?

1 vulnerability was recorded for form-data in the last 12 months, and the oldest entry in this database dates to 21 Jul 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of form-data are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor form-data for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the form-data version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.