CVE-2026-46510: Prototype pollution in form-data-objectizer via bracket-notation form keys
form-data-objectizer converts FormData to object. Prior to 1.0.1, form-data-objectizer walks bracket-notation form keys (e.g. name[sub]) into nested objects without filtering __proto__, constructor, or prototype. A single HTTP form field whose name starts with __proto__[...] causes the library to mutate Object.prototype, which is a prototype pollution primitive of the entire Node.js process. This vulnerability is fixed in 1.0.1.
Security readout for executives and security teams
Plain-English summary
A vulnerable form parsing helper can let an unauthenticated web request poison shared JavaScript object behavior inside a Node.js process. That can corrupt server-side logic and may cause availability impact depending on how the application uses parsed form data. Organizations using form-data-objectizer below 1.0.1 should update promptly.
Executive priority
Treat this as a prompt patching item for any internet-facing Node.js service using the package. It is not currently sourced as exploited, but the combination of unauthenticated reachability and integrity impact justifies fast dependency remediation.
Technical view
form-data-objectizer before 1.0.1 walks bracket-notation FormData keys into nested objects without blocking prototype-related keys. The advisory describes mutation of Object.prototype, creating a process-wide prototype pollution primitive. The published CVSS is 8.2, with network attack vector, low complexity, no privileges, and no user interaction.
Likely exposure
Exposure is likely limited to Node.js applications that depend on form-data-objectizer below 1.0.1 and pass attacker-controlled FormData into it. Public routes handling web forms, API multipart submissions, or framework adapters using this library deserve priority review.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. The risk is still material because the issue is unauthenticated, remotely reachable where vulnerable form parsing is exposed, and prototype pollution can alter downstream application logic in hard-to-predict ways.
Researcher notes
CWE-1321 applies. The fix is associated with upstream advisory GHSA-m2hg-wjq3-28wq and commit 7c54b99408e6e9cd6533b7245bf197dadc2a2dbc. Evidence in the provided bundle supports affected versions below 1.0.1 only; do not generalize to other form parsers without separate proof.
Mitigation direction
Upgrade form-data-objectizer to version 1.0.1 or later.
Regenerate lockfiles and confirm production builds resolve the patched version.
If immediate upgrade is blocked, check vendor guidance for supported mitigations.
Restrict untrusted form parsing paths until dependency remediation is complete.
Add input validation around unexpected prototype-related form field names.
Validation and detection
Search dependency manifests and lockfiles for form-data-objectizer versions below 1.0.1.
Identify public routes that parse attacker-controlled FormData with this library.
Confirm deployed artifacts use the patched package, not only source branches.
Add regression tests for prototype-related bracket keys without using offensive payloads.
Review logs for anomalous form field names on affected endpoints.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1321: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-1321 · source CWE mapping
Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.