npm package report

Is parse-nested-form-data safe?

1 known vulnerability, worst severity HIGH.

cvss
8.2

how bad it is if exploited, out of 10

epss
0.30%

chance of exploitation in the next 30 days

xyz score
3.3

CyberXYZ composite, out of 10

fig. 01 — GHSA-xp7r-j8r6-j9h3, the advisory selected below

// advisories

GHSA-xp7r-j8r6-j9h3

HIGHCVE-2026-45302

parseFormData() walks bracket and dot-notation FormData field names into nested objects without filtering reserved property keys. A single FormData field whose name begins with proto, or contains .proto. mid-path, causes the parser to traverse onto Object.prototype and assign properties there, polluting the prototype chain of every plain object in the running process.

Affected
<= 1.0.0, >=0, <1.0.1
Fixed in
1.0.1
Weakness
CWE-1321
Published
2026-05-18
Source
github

GHSANVDMITREreferencereferencereference

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 01:37 UTC. The most recent advisory here was published 2026-05-18. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is parse-nested-form-data safe? npm package security report | CyberXYZ